From: Richard Stallman <rms@santafe.edu>
To: fnf@ninemoons.com
Cc: egcs@cygnus.com, rms@santafe.edu
Subject: Re: Please help merge the major changes
Date: Mon, 27 Apr 1998 21:29:00 -0000 [thread overview]
Message-ID: <199804280139.TAA14877@wijiji.santafe.edu> (raw)
In-Reply-To: <199804261712.KAA19667@ninemoons.com>
The CVS repository contains an entire
progression of EGCS source trees, from the time the project was
started, until now. Anyone wanting to start with the most recent
tagged source tree, or any intermediate source tree, can just do
merging work directly from that...
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.
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.
next prev parent reply other threads:[~1998-04-27 21:29 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 [this message]
1998-04-28 10:26 ` Joe Buck
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=199804280139.TAA14877@wijiji.santafe.edu \
--to=rms@santafe.edu \
--cc=egcs@cygnus.com \
--cc=fnf@ninemoons.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).