From: Ranjit Mathew <rmathew@hotmail.com>
To: gcc@gcc.gnu.org
Subject: Re: Heads up: today's GCC snapshot
Date: Tue, 20 May 2003 04:50:00 -0000 [thread overview]
Message-ID: <3EC9B3E0.2010704@hotmail.com> (raw)
In-Reply-To: <Pine.BSF.4.55.0305191728310.3171@naos.dbai.tuwien.ac.at>
Gerald Pfeifer wrote:
> I have modified the gcc_release script on gcc.gnu.org to put diff files
> into a "diffs" subdirectory of the release/snapshots directory and am
> going to test this change as part of todays's snapshot problem.
>
> Should any problems arise, I am willing and prepared to address them this
> evening.
>
> Don't panic. :-)
Ok, not for *this* reason, but I'm panicking nevertheless... :-)
The latest (20030519) snapshot shows a 3.3.1 prerelease
version and not 3.4 prerelease as I had expected.
Due to bandwidth constraints, during the 3.3 cycle I
initially downloaded an early 3.3 snapshot and then
I used to update it every week with the weekly
snapshot diffs.
This allowed me to keep up with 3.3 (especially w.r.t.
GCJ) and be able to submit relevant patches.
Now I want to work with the bleeding edge 3.4, but
the snapshots are moving in a different direction.
What can I do? When will the snapshots move to 3.4?
What's the point of maintaining snapshots of
the 3.3 branch now?
BTW, this page:
http://gcc.gnu.org/snapshots.html
should be updated with the status of the snapshots
w.r.t. to the various GCC branches at a given time
and "roadmap" for the snapshots vis-a-vis these
branches.
For example, when 3.3 branched off, the snapshots
took that road instead of continuing with MAIN. Now
that 3.3 has been released, should the snapshots
not "come back"? Or does it happen only during Stage 2
of the MAIN branch?
Thanks in advance for any help.
Ranjit.
--
Ranjit Mathew Email: rmathew AT hotmail DOT com
Bangalore, INDIA. Web: http://ranjitmathew.tripod.com/
next prev parent reply other threads:[~2003-05-20 4:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-19 15:41 Gerald Pfeifer
2003-05-20 4:50 ` Ranjit Mathew [this message]
2003-05-20 20:48 ` Gerald Pfeifer
2003-05-21 6:34 ` Ranjit Mathew
2003-05-23 23:59 ` Gerald Pfeifer
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=3EC9B3E0.2010704@hotmail.com \
--to=rmathew@hotmail.com \
--cc=gcc@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).