public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at redhat dot com" <sourceware-bugzilla@sources.redhat.com>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/765] libio/fmemopen.c: trunk change needed on glibc-2_3-branch
Date: Tue, 15 Mar 2005 08:10:00 -0000	[thread overview]
Message-ID: <20050315081002.21866.qmail@sourceware.org> (raw)
In-Reply-To: <20050225101816.765.schwinge-bugzilla-sources.redhat.com@nic-nac-project.de>


------- Additional Comments From jakub at redhat dot com  2005-03-15 08:09 -------
Fixed in CVS.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |RESOLVED
         Resolution|                            |FIXED


http://sources.redhat.com/bugzilla/show_bug.cgi?id=765

------- 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:[~2005-03-15  8:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-25 10:18 [Bug libc/765] New: " schwinge-bugzilla-sources dot redhat dot com at nic-nac-project dot de
2005-02-25 10:20 ` [Bug libc/765] " schwinge-bugzilla-sources dot redhat dot com at nic-nac-project dot de
2005-03-01  4:02 ` gotom at debian dot or dot jp
2005-03-01 20:57 ` cvs-commit at gcc dot gnu dot org
2005-03-01 20:58 ` roland at gnu dot org
2005-03-15  8:10 ` jakub at redhat dot com [this message]
     [not found] <bug-765-131@http.sourceware.org/bugzilla/>
2011-03-16 21:32 ` roland at gnu dot org
2012-04-28  2:30 ` mtk.manpages at gmail dot com
2012-04-28  2:35 ` mtk.manpages at gmail 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=20050315081002.21866.qmail@sourceware.org \
    --to=sourceware-bugzilla@sources.redhat.com \
    --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).