From: Joe Buck <jbuck@synopsys.com>
To: rms@gnu.org
Cc: fnf@ninemoons.com, egcs@cygnus.com, rms@santafe.edu
Subject: Re: Please help merge the major changes
Date: Tue, 28 Apr 1998 10:26:00 -0000 [thread overview]
Message-ID: <199804281644.JAA11113@atrus.synopsys.com> (raw)
In-Reply-To: <199804280139.TAA14877@wijiji.santafe.edu>
> You're right that CVS helps here. Making changes in EGCS today won't
> interfere with the specific job of merging a certain change that was
> present in EGCS yesterday. But the issue at hand goes beyond that.
Yes, we must decide what to merge and how.
> Right now, certain features in EGCS are mature and it's time to put
> them into GCC releases. But there will be more in the future. In
> addition to moving certain changes to the GCC release now, we need to
> have a smooth flow of changes from EGCS to GCC releases over the long
> haul.
CVS provides a good mechanism for doing this. This mechanism is already
demonstrated to be working in the EGCS tree, with 1.0.x managed for
maximum stability (it is considerably more stable than 2.8.1 and vastly
more stable than the gcc2 snapshots) without interfering with the main
development branch.
What we should work towards is this: EGCS and GCC share the same
CVS development tree, and what we are now calling the stable EGCS
branch should be called GCC. The simplest way to do this is to
merge GCC into EGCS, not to try to extract EGCS pieces for movement
into GCC.
prev parent reply other threads:[~1998-04-28 10:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-04-25 23:24 Richard Stallman
1998-04-26 10:26 ` Fred Fish
1998-04-27 21:29 ` Richard Stallman
1998-04-28 10:26 ` Joe Buck [this message]
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=199804281644.JAA11113@atrus.synopsys.com \
--to=jbuck@synopsys.com \
--cc=egcs@cygnus.com \
--cc=fnf@ninemoons.com \
--cc=rms@gnu.org \
--cc=rms@santafe.edu \
/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).