public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "drepper at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug admin/2123] tracker for 2.3.7 release requirements - DO NO TOUCH YOURSELF
Date: Sun, 18 Feb 2007 04:47:00 -0000	[thread overview]
Message-ID: <20070218044655.18623.qmail@sourceware.org> (raw)
In-Reply-To: <20060107233130.2123.roland@gnu.org>



-- 
Bug 2123 depends on bug 2013, which changed state.

Bug 2013 Summary: memccpy() gives inconsistent results on mmapped files
http://sourceware.org/bugzilla/show_bug.cgi?id=2013

           What    |Old Value                   |New Value
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
         Resolution|                            |FIXED

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

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


  parent reply	other threads:[~2007-02-18  4:47 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-07 23:31 [Bug admin/2123] New: " roland at gnu dot org
2006-01-07 23:31 ` [Bug admin/2123] " roland at gnu dot org
2006-02-21  2:29 ` roland at gnu dot org
2006-02-21  2:32 ` roland at gnu dot org
2006-02-21  2:33 ` roland at gnu dot org
2006-02-23 22:36 ` roland at gnu dot org
2006-03-02  4:50 ` roland at gnu dot org
2007-02-18  4:47 ` drepper at redhat dot com [this message]
2007-07-01 22:57 ` samuel dot thibault at ens-lyon dot org
2007-07-21 20:29 ` samuel dot thibault at ens-lyon dot org
2007-07-21 21:43 ` samuel dot thibault at ens-lyon dot org
2010-09-02 15:41 ` schwab at linux-m68k dot org

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=20070218044655.18623.qmail@sourceware.org \
    --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).