This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Moving to git
- From: Andi Kleen <andi at firstfloor dot org>
- To: Jason Merrill <jason at redhat dot com>
- 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: Wed, 26 Aug 2015 09:38:21 -0700
- Subject: Re: Moving to git
- 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>
Jason Merrill <jason@redhat.com> writes:
>
> You don't even need to worry about the hash code, you can use the
> timestamp by itself. Given the timestamp,
>
> git log -1 --until 1440153969
Consider tree merges. There's no guarantee a time stamp maps to
monotonically increasing commit numbers.
But I don't really understand the problem. Just run git log
and generate your own list of numbers. Should be straight forward
to script.
-Andi
--
ak@linux.intel.com -- Speaking for myself only