From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Gary Funck <gary@intrepid.com>
Cc: Gcc Patches <gcc-patches@gcc.gnu.org>,
Gerald Pfeifer <gerald@pfeifer.com>
Subject: Re: gcc_release script, snapshots, and LAST_UPDATED version
Date: Mon, 20 Dec 2010 17:52:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.1012201641530.6154@digraph.polyomino.org.uk> (raw)
In-Reply-To: <20101220160327.GX24726@intrepid.com>
On Mon, 20 Dec 2010, Gary Funck wrote:
> On 12/20/10 11:54:51, Joseph S. Myers wrote:
> > It's LAST_UPDATED, not LAST_CHANGED. This is significant; the revision
> > number is indeed the revision at which the source tree was last updated,
> > not the revision at which the branch was last changed.
>
> OK. How is LAST_UPDATED more useful than LAST_CHANGED? I would have
> thought that it would be useful to know the last version on the branch
> that is being snap-shotted.
I think you should be doing your own interrogation of SVN information in
your snapshot script. This file is for convenient identification of
checkouts for the use of scripts such as contrib/test_summary; the
information it contains is already formally redundant (both revision and
date, in different time zones). It is not meant to contain everything
that could possibly be of use in describing a checkout, and certainly not
everything relevant for making a snapshot decision (for normal GCC
snapshots, you might want to skip them if only the DATESTAMP file -
checked in - had been updated since the last snapshot).
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2010-12-20 16:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-20 11:08 Gary Funck
2010-12-20 15:07 ` Joseph S. Myers
2010-12-20 17:36 ` Gary Funck
2010-12-20 17:52 ` Joseph S. Myers [this message]
2011-01-28 20:01 ` Gerald Pfeifer
2011-01-28 20:42 ` Joseph S. Myers
2011-01-28 23:55 ` Gerald Pfeifer
2011-01-29 17:09 ` Gary Funck
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=Pine.LNX.4.64.1012201641530.6154@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=gary@intrepid.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gerald@pfeifer.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).