From: Jeffrey A Law <law@cygnus.com>
To: egcs@cygnus.com
Subject: New STL & egcs
Date: Wed, 08 Jul 1998 20:00:00 -0000 [thread overview]
Message-ID: <14102.899952980@hurl.cygnus.com> (raw)
BTW, I should have mentioned that I'm considering running egcs-1.2
off the same branch as egcs-1.1.
ie, we go through the egcs-1.1 release cycle, possibly making a few
minor releases as we deem it necessary.
Then we add the new STL code (and only the new STL code) to the release
branch and start the egcs-1.2 cycle. That way we don't have to go through
the process of stabilizing the entire tree again -- which should allow
us to get egcs-1.2 out relatively quickly. ie, egcs-1.2 works like
a minor release, except that it's got the new STL code.
I haven't discussed this with the steering committee, but it is one
way we can avoid adding the STL code to egcs-1.1 and still get a
release out with that code in a relatively short timeframe.
jeff
next reply other threads:[~1998-07-08 20:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-07-08 20:00 Jeffrey A Law [this message]
1998-07-09 8:45 ` Joe Buck
1998-07-10 7:25 ` Ben Scherrey
[not found] ` <199807091455.HAA04686.cygnus.egcs@atrus.synopsys.com>
1998-07-09 17:40 ` Nathan Myers
1998-07-10 0:33 Anthony Shipman
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=14102.899952980@hurl.cygnus.com \
--to=law@cygnus.com \
--cc=egcs@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).