[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#133336: marked as done (glibc-doc: return type of cfmakeraw is void, not int)

Your message dated Sun, 24 Jul 2005 05:16:08 +0900
with message-id <81sly5nurb.wl%gotom@debian.or.jp>
and subject line Bug#133336: 133336: glibc-doc: return type of cfmakeraw is void, not int
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

Received: (at submit) by bugs.debian.org; 11 Feb 2002 06:56:21 +0000
>From oohara@libra.interq.or.jp Mon Feb 11 00:56:21 2002
Return-path: <oohara@libra.interq.or.jp>
Received: from smtp02.mem.interq.net [] 
	by master.debian.org with esmtp (Exim 3.12 1 (Debian))
	id 16aANw-0004yR-00; Mon, 11 Feb 2002 00:56:20 -0600
Received: from grain (kyoto-ppp-210-172-160-110.interq.or.jp [])
	by smtp02.mem.interq.net (8.9.3/8.9.1) with ESMTP id PAA00069
	for <submit@bugs.debian.org>; Mon, 11 Feb 2002 15:56:11 +0900 (JST)
Received: from localhost ([] ident=oohara)
	by grain with esmtp (Exim 3.33 #1 (Debian))
	id 16aAOz-0000qr-00; Mon, 11 Feb 2002 15:57:25 +0900
Date: Sun, 10 Feb 2002 19:25:22 +0900 (JST)
Message-Id: <20020210.192522.74737494.oohara@grain>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Cc: oohara@libra.interq.or.jp
Subject: glibc-doc: return type of cfmakeraw is void, not int
X-Debbugs-CC: Oohara Yuuma <oohara@libra.interq.or.jp>
From: Oohara Yuuma <oohara@libra.interq.or.jp>
X-Mailer: Mew version 2.1.52 on Emacs 21.1 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Delivered-To: submit@bugs.debian.org

Package: glibc-doc
Version: 2.2.4-7
Severity: normal

info manual of glibc-doc says:
 - Function: int cfmakeraw (struct termios *TERMIOS-P)

/usr/include/termios.h says:
extern void cfmakeraw (struct termios *__termios_p) __THROW;

-- System Information
Debian Release: 2.2
Kernel Version: Linux grain 2.4.16 #1 Thu Jan 10 00:18:21 JST 2002 i686 unknown

hi  libc6-dev      2.2.4-7        GNU C Library: Development Libraries and Hea

Received: (at 133336-done) by bugs.debian.org; 23 Jul 2005 20:16:19 +0000
>From gotom@debian.or.jp Sat Jul 23 13:16:19 2005
Return-path: <gotom@debian.or.jp>
Received: from omega.webmasters.gr.jp (webmasters.gr.jp) [] 
	by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
	id 1DwQPz-0004pa-00; Sat, 23 Jul 2005 13:16:19 -0700
Received: from omega.webmasters.gr.jp (localhost [])
	by webmasters.gr.jp (Postfix) with ESMTP id B9F36DEB83;
	Sun, 24 Jul 2005 05:16:08 +0900 (JST)
Date: Sun, 24 Jul 2005 05:16:08 +0900
Message-ID: <81sly5nurb.wl%gotom@debian.or.jp>
From: GOTO Masanori <gotom@debian.or.jp>
To: "Michael Kerrisk" <mtk-manpages@gmx.net>,
Cc: Martin Schulze <joey@infodrom.org>
Subject: Re: Bug#133336: 133336: glibc-doc: return type of cfmakeraw is void, not int
In-Reply-To: <26974.1119012868@www9.gmx.net>
References: <20041220165956.GO7329@finlandia.infodrom.north.de>
User-Agent: Wanderlust/2.11.30 (Wonderwall) SEMI/1.14.6 (Maruoka) FLIM/1.14.6 (Marutamachi) APEL/10.6 Emacs/21.4 (i386-pc-linux-gnu) MULE/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Delivered-To: 133336-done@bugs.debian.org
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
	(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER 
	autolearn=no version=2.60-bugs.debian.org_2005_01_02

At Fri, 17 Jun 2005 14:54:28 +0200 (MEST),
Michael Kerrisk wrote:
> Why is this report still open?  Things were long ago fixed
> the manual pages, and in the glibc docs.

Yes, I think this bug was already fixed, too.  I close this bug now.

-- gotom

Reply to: