From: Andreas Jaeger <aj@suse.de>
To: libc-hacker@sources.redhat.com
Subject: Fix glibcbug references
Date: Sat, 27 Oct 2007 15:53:00 -0000 [thread overview]
Message-ID: <87zly4o8og.fsf@suse.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 3704 bytes --]
Ok to commit the following? glibcbug does not exist anymore,
Andreas
2007-10-27 Andreas Jaeger <aj@suse.de>,
[BZ #5120]
* FAQ.in: Reference bugzilla instead of glibcbug script.
* BUGS: Likewise.
* intl/locale.alias: Likewise.
============================================================
Index: FAQ.in
--- FAQ.in 8 Apr 2005 20:59:50 -0000 1.137
+++ FAQ.in 27 Oct 2007 15:53:34 -0000
@@ -287,12 +287,12 @@ down the build process and need more dis
failure should be looked into. Depending on the failures, you probably
should not install the library at all.
-You should consider using the `glibcbug' script to report the failure,
-providing as much detail as possible. If you run a test directly, please
-remember to set up the environment correctly. You want to test the compiled
-library - and not your installed one. The best way is to copy the exact
-command line which failed and run the test from the subdirectory for this
-test in the sources.
+You should consider reporting it in bugzilla
+<http://sourceware.org/bugzilla/> providing as much detail as possible.
+If you run a test directly, please remember to set up the environment
+correctly. You want to test the compiled library - and not your installed
+one. The best way is to copy the exact command line which failed and run
+the test from the subdirectory for this test in the sources.
There are some failures which are not directly related to the GNU libc:
- Some compilers produce buggy code. No compiler gets single precision
============================================================
Index: BUGS
--- BUGS 23 Sep 2005 20:27:08 -0000 1.46
+++ BUGS 27 Oct 2007 15:53:34 -0000
@@ -12,12 +12,10 @@ GNU project. There is an easy to use WW
http://sourceware.org/bugzilla/
-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. Before reporting
-a bug please check the FAQ since it discusses also a lot of problematic
-situations.
+I would appreciate it very much if you could verify the problem was
+not reported before by looking through the database. Before reporting
+a bug please check the FAQ since it discusses also a lot of
+problematic situations.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
============================================================
Index: intl/locale.alias
--- intl/locale.alias 4 Dec 2003 07:57:47 -0000 1.23
+++ intl/locale.alias 27 Oct 2007 15:53:34 -0000
@@ -1,5 +1,5 @@
# Locale name alias data base.
-# Copyright (C) 1996-2001,2003 Free Software Foundation, Inc.
+# Copyright (C) 1996-2001,2003,2007 Free Software Foundation, Inc.
#
# This program is free software; you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
@@ -23,8 +23,8 @@
# Note: This file is far from being complete. If you have a value for
# your own site which you think might be useful for others too, share
-# it with the rest of us. Send it using the `glibcbug' script to
-# bugs@gnu.org.
+# it with the rest of us. Report it in our bugzilla at
+# http://sourceware.org/bugzilla/ .
bokmal nb_NO.ISO-8859-1
bokmål nb_NO.ISO-8859-1
--
Andreas Jaeger, Director Platform / openSUSE, aj@suse.de
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
Maxfeldstr. 5, 90409 Nürnberg, Germany
GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
[-- Attachment #2: Type: application/pgp-signature, Size: 193 bytes --]
next reply other threads:[~2007-10-27 15:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-27 15:53 Andreas Jaeger [this message]
2007-10-28 1:41 ` Ulrich Drepper
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zly4o8og.fsf@suse.de \
--to=aj@suse.de \
--cc=libc-hacker@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).