public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug libc/11878] New: 'glibc' build documentation is apparently incomplete
@ 2010-08-04 10:35 sergstesh at yahoo dot com
0 siblings, 0 replies; only message in thread
From: sergstesh at yahoo dot com @ 2010-08-04 10:35 UTC (permalink / raw)
To: glibc-bugs
In http://sourceware.org/bugzilla/show_bug.cgi?id=11875#c10 one can read:
"
Of course this is a 333 dup. Don't ever file build problem reports in BZ. This
is what mailing lists are for.
".
So, the lead 'glibc' developer openly claims one can't get knowledge on how to
build 'glibc' in places other than mailing list.
I think that the logical place to look for such knowledge is the documentation
which comes with the source.
Just wondering - is the official RedHat policy ? I.e. does RedHat think that
users of its software should look for info in mailing lists rather than in the
documentation which comes with the software ?
--
Summary: 'glibc' build documentation is apparently incomplete
Product: glibc
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: libc
AssignedTo: drepper at redhat dot com
ReportedBy: sergstesh at yahoo dot com
CC: glibc-bugs at sources dot redhat dot com
http://sourceware.org/bugzilla/show_bug.cgi?id=11878
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2010-08-04 10:35 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2010-08-04 10:35 [Bug libc/11878] New: 'glibc' build documentation is apparently incomplete sergstesh at yahoo dot com
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).