From: Mark Mitchell <mark@codesourcery.com>
To: Toon Moene <toon@moene.indiv.nluug.nl>,
"Joseph S. Myers" <jsm28@cam.ac.uk>
Cc: gcc@gcc.gnu.org
Subject: Re: GCC 3.1 Branch
Date: Sun, 24 Feb 2002 23:26:00 -0000 [thread overview]
Message-ID: <2040000.1014601137@localhost> (raw)
In-Reply-To: <3C76988D.9866B9E@moene.indiv.nluug.nl>
--On Friday, February 22, 2002 08:14:21 PM +0100 Toon Moene
<toon@moene.indiv.nluug.nl> wrote:
> "Joseph S. Myers" wrote:
>
>> * All [vV]ersion.c files on the mainline, to say 3.2 instead of 3.1 (and
>> to say 0.5.28 as the G77 version number, since the separate G77 version
>> number hasn't been eliminated yet).
>
> If there's consensus about this issue, I'm all for removing the separate
> g77 and libf2c version numbers. Just say so and I will effect it once
> the 3.2 branch is created.
Nobody has spoken out against, and I am for, so let's call that
consensus.
If you can, try to reduce the total number of version.c files in the
process.
Thanks,
--
Mark Mitchell mark@codesourcery.com
CodeSourcery, LLC http://www.codesourcery.com
next prev parent reply other threads:[~2002-02-25 7:21 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-21 16:48 Mark Mitchell
2002-02-21 17:25 ` Joseph S. Myers
2002-02-22 2:06 ` Joseph S. Myers
2002-02-22 12:15 ` Toon Moene
2002-02-24 23:26 ` Mark Mitchell [this message]
2002-02-25 20:28 ` David O'Brien
2002-02-21 18:29 Richard Kenner
2002-02-21 19:03 ` David Edelsohn
2002-02-21 19:29 ` Alexandre Oliva
2002-02-21 20:41 ` H . J . Lu
2002-02-21 21:02 ` David Edelsohn
2002-02-21 19:05 ` Alexandre Oliva
2002-02-26 0:40 Mark Mitchell
2002-02-26 8:25 ` Corey Minyard
2002-02-26 9:45 ` Mark Mitchell
2002-05-15 18:48 Mark Mitchell
2002-05-16 21:07 ` Aldy Hernandez
2002-05-16 23:02 ` Daniel Jacobowitz
2002-05-16 23:09 ` Aldy Hernandez
2002-05-17 0:21 ` Mark Mitchell
2002-05-16 23:35 ` Mark Mitchell
2002-05-17 0:34 ` Aldy Hernandez
2002-05-17 1:21 ` Mark Mitchell
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=2040000.1014601137@localhost \
--to=mark@codesourcery.com \
--cc=gcc@gcc.gnu.org \
--cc=jsm28@cam.ac.uk \
--cc=toon@moene.indiv.nluug.nl \
/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).