This is the mail archive of the libc-hacker@sources.redhat.com mailing list for the glibc project.

Note that libc-hacker is a closed list. You may look at the archives of this list, but subscription and posting are not open.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: BUGS file

From: Jakub Jelinek <jakub at redhat dot com>
To: Roland McGrath <roland at redhat dot com>
Cc: Ulrich Drepper <drepper at redhat dot com>, GNU libc hackers <libc-hacker at sources dot redhat dot com>
Date: Wed, 30 Jun 2004 08:24:21 +0200
Subject: Re: BUGS file
References: <40E0A843.1000703@redhat.com> <200406282334.i5SNYPXZ002898@magilla.sf.frob.com>
Reply-to: Jakub Jelinek <jakub at redhat dot com>

On Mon, Jun 28, 2004 at 04:34:25PM -0700, Roland McGrath wrote:
> Well, whatever.  I still think using bugzilla for these long-term items is
> fine.  But at the very least, we need to clean stale items out of the BUGS
> file.

And update the bugreporting instructions in there:

Another source of information about bugs is the problem data base of the
GNU project.  There is an easy to use WWW interface available at

       http://www-gnats.gnu.org:8080/cgi-bin/wwwgnats.pl

I would appreciate it very much if you could verify the problem was not
reported before by looking through the database.  To make the information
in this database as useful as possible please report bugs always using the
`glibcbug' shell script which gets installed with GNU libc.

	Jakub

References:
- Re: BUGS file
  - From: Ulrich Drepper
- Re: BUGS file
  - From: Roland McGrath

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]