Re: [PATCH] [RFD] Add repoid identifier to commit

From: Sean <seanlkml@sympatico.ca>
Date: May 12, 2005, 10:39 UTC
Message-ID: <3019.10.10.10.24.1115894386.squirrel@linux1>
In-Reply-To: <1115892451.16187.561.camel@hades.cambridge.redhat.com>

On Thu, May 12, 2005 6:07 am, David Woodhouse said:

Show 25 quoted lines

> On Wed, 2005-05-11 at 20:58 -0400, Sean wrote:
>> > Try to find out the history of kernel.org/.../dwmw2/audit-2.6 in
>> > correct order, using the available tools.
>> >
>> > Come back to me when you are done.
>>
>> Ask me any question that matters and i'll answer it with available
>> tools.
>
> The above question matters, so please answer it if you can. I'll make it
> clearer for you though...
>
> By 'correct order' Thomas means the order in which my old BK-export
> script used to generate the "changesets since last release" web page;
> the order in which the changes actually got merged into Linus'
> repository.
>
> If I looked at the page yesterday, and then I look at it again today, I
> want all the commits I hadn't seen already to be at the _top_.
> Regardless of the date on which they were _originally_ committed to some
> private tree elsewhere.
>
> There were a lot of complaints until I worked out how to get that
> ordering out of BitKeeper.
>

Actually, here is one very simple idea, just use the times from the object files themselves. Now as you descend the hierarchy you can simply stat the object file to get the "local commit time". Just simply stop descending down each branch when you find a commit with a time stamp that is outside the range you're interested in.

Sean