public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Robert Wilhelm <robert@physiol.med.tu-muenchen.de>
To: "H.J. Lu" <hjl@lucon.org>
Cc: Jason Merrill <jason@cygnus.com>, law@cygnus.com, egcs@cygnus.com
Subject: Re: libio patches for glibc 2.1
Date: Thu, 26 Feb 1998 20:35:00 -0000	[thread overview]
Message-ID: <19980226092316.51232@haegar.physiol.med.tu-muenchen.de> (raw)
In-Reply-To: <m0y7tjf-00058gC@ocean.lucon.org>

On Wed, Feb 25, 1998 at 07:11:47PM -0800, H.J. Lu wrote:
> 
> I think that fix breaks glibc 2.1 and glibc 2.0.7.
>

IMHO this should not hurt at all, since glibc 2.1 and glibc 2.0.7
are not yet released and could propably be fixed.

Robert


  parent reply	other threads:[~1998-02-26 20:35 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-02-23  2:16 Andreas Schwab
1998-02-23 11:54 ` H.J. Lu
1998-02-23 11:54   ` Ulrich Drepper
1998-02-23 11:54     ` H.J. Lu
1998-02-23 11:00       ` Ulrich Drepper
1998-02-23 11:00         ` H.J. Lu
1998-02-23 11:54           ` Ulrich Drepper
1998-02-23 13:07             ` H.J. Lu
1998-02-23 14:09             ` Joe Buck
1998-02-23 15:08               ` Ulrich Drepper
1998-02-23 15:08                 ` Joe Buck
1998-02-23 15:24                   ` Ulrich Drepper
1998-02-23 15:31                     ` Joe Buck
1998-02-23 15:34                       ` Ulrich Drepper
1998-02-24  3:09             ` Jeffrey A Law
1998-02-25  9:33   ` Jeffrey A Law
1998-02-25 11:32     ` H.J. Lu
     [not found]   ` <1949.888379825.cygnus.egcs@hurl.cygnus.com>
1998-02-25 11:32     ` Jason Merrill
1998-02-25 19:12       ` H.J. Lu
1998-02-25 20:56         ` Jason Merrill
1998-03-05 16:38           ` H.J. Lu
1998-02-26 20:35         ` Robert Wilhelm [this message]
1998-03-05 16:38           ` H.J. Lu
1998-02-25  9:33 ` Jeffrey A Law
1998-02-23 15:57 Mike Stump

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=19980226092316.51232@haegar.physiol.med.tu-muenchen.de \
    --to=robert@physiol.med.tu-muenchen.de \
    --cc=egcs@cygnus.com \
    --cc=hjl@lucon.org \
    --cc=jason@cygnus.com \
    --cc=law@cygnus.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).