This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Help with changing snapshot mechanism
- From: "Joseph S. Myers" <jsm at polyomino dot org dot uk>
- To: Gerald Pfeifer <gerald at pfeifer dot com>
- Cc: Mark Mitchell <mark at codesourcery dot com>, gcc at gcc dot gnu dot org, obrien at FreeBSD dot org
- Date: Sat, 17 Jan 2004 20:00:19 +0000 (UTC)
- Subject: Re: Help with changing snapshot mechanism
- References: <Pine.BSF.4.58.0401172015390.46782@acrux.dbai.tuwien.ac.at>
On Sat, 17 Jan 2004, Gerald Pfeifer wrote:
> The policy I had in mind was not making snapshots from mainline until
> x.y.0 has been released, to put a stronger focus on release work and
> especially testing, so for now I'd like us to only provide snapshots
> of the 3.3 and 3.4 branches.
What do the FreeBSD people (who seemed to make the most calls for
snapshots from both mainline and branches so that snapshot URLs could be
used for ports, e.g. <http://gcc.gnu.org/ml/gcc/2002-03/msg00344.html>)
think of this?
> I think I can make this work (even though I have never used this aspect
> of the script before. How about me running a manual first snapshot for
> 3.5, to get the branching done right, even if we won't provide regular
> snapshots until 3.4.0 has been released?
That seems reasonable (the diffs support is very general - running the
script manually you could build a release with diffs from the previous
release, and diffs from the previous prerelease, and diffs from the last
snapshot on that branch - but the snapshot mode presently hardcodes the
version number for the diffs to be the same as that for the new snapshot:
OLD_TARS=${LAST_DIR}/gcc-${BRANCH}-${LAST_DATE}.tar.bz2
).
--
Joseph S. Myers
jsm@polyomino.org.uk