From: Matthew Wilcox <willy@debian.org>
To: jsoe0708@tiscali.be
Cc: parisc-linux@parisc-linux.org
Subject: Re: [parisc-linux] GCC CVS strange update?
Date: Tue, 30 Jul 2002 07:30:09 +0100 [thread overview]
Message-ID: <20020730073009.N1441@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <3D38181A000003D9@ocpmta6.be.tiscali.com>; from jsoe0708@tiscali.be on Tue, Jul 30, 2002 at 08:27:39AM +0200
On Tue, Jul 30, 2002 at 08:27:39AM +0200, jsoe0708@tiscali.be wrote:
> Yesterday morning I do a cvs update of what I believe till last week being
> gcc-3.1
> (CVS/Tag == Tgcc-3-1-branch) but gcc/gcc/version.c shows me now 3.2 (well
> the current development CVS being now 3.3)?
ah, you haven't been following the gcc mailing list. due to a pressing
need to change the c++ ABI, the current 3.1 development tree has been
renamed to 3.2 and the erstwhile 3.2 development line has been renamed
to 3.3.
--
Revolutions do not require corporate support.
next prev parent reply other threads:[~2002-07-30 6:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-30 6:27 [parisc-linux] GCC CVS strange update? jsoe0708
2002-07-30 6:30 ` Matthew Wilcox [this message]
2002-07-30 15:33 ` John David Anglin
2002-07-30 19:20 ` Carlos O'Donell
2002-07-30 19:40 ` Matthew Wilcox
2002-07-30 20:04 ` John David Anglin
2002-07-30 19:53 ` John David Anglin
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=20020730073009.N1441@parcelfarce.linux.theplanet.co.uk \
--to=willy@debian.org \
--cc=jsoe0708@tiscali.be \
--cc=parisc-linux@parisc-linux.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: 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