public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Mark Mitchell <mark@codesourcery.com> To: pme@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org Subject: Re: libstdc++/2071 Date: Tue, 12 Jun 2001 02:06:00 -0000 [thread overview] Message-ID: <20010612090603.25488.qmail@sourceware.cygnus.com> (raw) The following reply was made to PR libstdc++/2071; it has been noted by GNATS. From: Mark Mitchell <mark@codesourcery.com> To: "rittle@labs.mot.com" <rittle@labs.mot.com>, "bkoz@redhat.com" <bkoz@redhat.com> Cc: "gcc-gnats@gcc.gnu.org" <gcc-gnats@gcc.gnu.org>, "pedwards@disaster.jaj.com" <pedwards@disaster.jaj.com> Subject: Re: libstdc++/2071 Date: Tue, 12 Jun 2001 02:04:48 -0700 --On Tuesday, June 12, 2001 03:53:38 AM -0500 Loren James Rittle <rittle@latour.rsch.comm.mot.com> wrote: > Hi Benjamin, > > (CC'd Mark so he knows what is going on as release manager. If you > don't have time to read the background, then feel free to jump to [MARK].) I think that we must fix this bug, and I think your approach is a good one. Thank you for taking the time to explain it in detail. If Benjamin does not reply, you may apply this patch at 3:00 PM on June 12th, GMT - 8. That will give Benjamin a chance to shout if he sees something wrong with it. You do need to add porting.texi information about the new _GLIBCPP_AVOID_FSEEK macro so that people know what it's for. You are doing an excellent job nailing lose ends. Thanks, -- Mark Mitchell mark@codesourcery.com CodeSourcery, LLC http://www.codesourcery.com
next reply other threads:[~2001-06-12 2:06 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-06-12 2:06 Mark Mitchell [this message] -- strict thread matches above, loose matches on Subject: below -- 2001-06-12 16:36 libstdc++/2071 Phil Edwards 2001-06-12 16:26 libstdc++/2071 Loren James Rittle 2001-06-12 13:26 libstdc++/2071 Benjamin Kosnik 2001-06-12 1:56 libstdc++/2071 Loren James Rittle 2001-06-11 19:06 libstdc++/2071 Benjamin Kosnik 2001-06-05 13:16 libstdc++/2071 pme
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=20010612090603.25488.qmail@sourceware.cygnus.com \ --to=mark@codesourcery.com \ --cc=gcc-prs@gcc.gnu.org \ --cc=pme@gcc.gnu.org \ /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: linkBe 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).