From: Tom Tromey <tromey@redhat.com>
To: Alan Modra <amodra@gmail.com>
Cc: Dmitry Samersoff <dms@samersoff.net>, gdb@sourceware.org
Subject: Re: Background of daily update changeset?
Date: Tue, 14 Jan 2014 14:36:00 -0000 [thread overview]
Message-ID: <87ppnuy6jj.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20140114005619.GN5390@bubble.grove.modra.org> (Alan Modra's message of "Tue, 14 Jan 2014 11:26:19 +1030")
>>>>> "Alan" == Alan Modra <amodra@gmail.com> writes:
Tom> My guess is that it's so that snapshots can be exactly identified.
Alan> Yes. HJ distributes his "Linux binutils", based on snapshots of
Alan> mainline plus some extra patches. Other people distribute snapshots
Alan> too. The date gives us some chance of tying Joe User's bug report to
Alan> the source.
Tom> FWIW I'm not really convinced it is all that useful.
Alan> I agree that it doesn't make much sense for gdb..
I'm curious how much use you really get out of it for binutils.
Alternatively, Would it be sufficient if "src-release" instead stuck the
git commit hash into some file?
It's not of major importance to me, more like a rainy day thing. But if
it's high value to you then I wouldn't change a thing.
Tom
prev parent reply other threads:[~2014-01-14 14:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-28 7:35 Dmitry Samersoff
2014-01-02 18:54 ` Paweł Sikora
2014-01-13 17:28 ` Tom Tromey
2014-01-14 0:56 ` Alan Modra
2014-01-14 14:36 ` Tom Tromey [this message]
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=87ppnuy6jj.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=amodra@gmail.com \
--cc=dms@samersoff.net \
--cc=gdb@sourceware.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