public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "joseph at codesourcery dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/14106] _FILE_OFFSET_BITS=64 goes outside standard namespace
Date: Mon, 14 May 2012 13:02:00 -0000	[thread overview]
Message-ID: <bug-14106-131-cTxtdcSM7D@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-14106-131@http.sourceware.org/bugzilla/>

http://sourceware.org/bugzilla/show_bug.cgi?id=14106

--- Comment #2 from joseph at codesourcery dot com <joseph at codesourcery dot com> 2012-05-14 13:01:44 UTC ---
On Mon, 14 May 2012, bugdal at aerifal dot cx wrote:

> This issue has been bothering me for a long time too, but I never thought to
> report it.

If you have any issues with glibc that can be represented as well-defined 
bugs - specific deficiencies for which it can be clearly assessed whether 
they have been fixed - and they don't have currently open bugs, please 
open (or reopen) bugs for them.  It doesn't matter how minor or obscure or 
hard to fix they are, we should track bugs in the bug database.  They may 
not be fixed particularly quickly - the existing bug backlog may take 
person-years of work across many people to deal with - but they should be 
filed so they are visible to people looking for bugs to fix.

(More open-ended projects for enhancement that don't represent a 
well-defined defect in current glibc may better go on the wiki than in 
Bugzilla; there are "Project TODO" and "Project Wishlist by Developer" 
sections there linking to pages with various suggestions.)

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


  parent reply	other threads:[~2012-05-14 13:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-14 10:51 [Bug libc/14106] New: " jsm28 at gcc dot gnu.org
2012-05-14 12:39 ` [Bug libc/14106] " bugdal at aerifal dot cx
2012-05-14 13:02 ` joseph at codesourcery dot com [this message]
2014-06-25 11:00 ` fweimer at redhat dot com

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=bug-14106-131-cTxtdcSM7D@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@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).