This is the mail archive of the
mailing list for the GCC project.
Re: Action stamps
- From: Jason Merrill <jason at redhat dot com>
- To: esr at thyrsus dot com, Andi Kleen <andi at firstfloor dot org>
- Cc: Richard Earnshaw <Richard dot Earnshaw at foss dot arm dot com>, Jakub Jelinek <jakub at redhat dot com>, Jeff Law <law at redhat dot com>, "gcc at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>
- Date: Sat, 29 Aug 2015 09:02:37 -0400
- Subject: Re: Action stamps
- Authentication-results: sourceware.org; auth=none
- References: <55D61512 dot 8010002 at redhat dot com> <55D61B23 dot 3000309 at redhat dot com> <55D63403 dot 4000603 at redhat dot com> <20150824081741 dot GB9425 at tucnak dot redhat dot com> <55DB3991 dot 4030701 at redhat dot com> <20150824154355 dot GM9425 at tucnak dot redhat dot com> <55DB3E2A dot 1030703 at foss dot arm dot com> <55DD36CE dot 9050707 at redhat dot com> <871teqf1j6 dot fsf at tassilo dot jf dot intel dot com> <20150826171133 dot GC2239 at thyrsus dot com>
On 08/26/2015 01:11 PM, Eric S. Raymond wrote:
What I usually do with old commit references in comments is map them
to what I call an "action stamp" - a user ID followed by an RFC3339
date. While this is theoretically not quite adequate, in practice
collisions are rare to nonexistent.
For general identification of commits, as with references automatically
added to Bugzilla and such, that makes a lot of sense. So in a git
format string, %ce and %cI. And we can map back from such a stamp to
the commit by specifying --author as well as --until; is that what you do?
For Jakub or anyone else wanting a key to associate a file with a
commit, they can decide for themselves what date format they want to use
and whether to bother with the user id. I would think that if he is
only interested in commits on the trunk (and so should use log
--first-parent), the timestamp is sufficient.