From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4926 invoked by alias); 14 May 2012 13:02:24 -0000 Received: (qmail 4917 invoked by uid 22791); 14 May 2012 13:02:24 -0000 X-SWARE-Spam-Status: No, hits=-3.7 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00,KHOP_THREADED X-Spam-Check-By: sourceware.org Received: from localhost (HELO sourceware.org) (127.0.0.1) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 14 May 2012 13:02:13 +0000 From: "joseph at codesourcery dot com" 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 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: libc X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: joseph at codesourcery dot com X-Bugzilla-Status: NEW X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated Content-Type: text/plain; charset="UTF-8" MIME-Version: 1.0 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org X-SW-Source: 2012-05/txt/msg00201.txt.bz2 http://sourceware.org/bugzilla/show_bug.cgi?id=14106 --- Comment #2 from 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.