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

From: Sean <seanlkml@sympatico.ca>
Date: May 12, 2005, 11:48 UTC
Message-ID: <2247.10.10.10.24.1115898521.squirrel@linux1>
In-Reply-To: <1115898230.11872.8.camel@tglx>

On Thu, May 12, 2005 7:43 am, Thomas Gleixner said:

Show 9 quoted lines

> On Thu, 2005-05-12 at 07:24 -0400, Sean wrote:
>> Right, that's what a fast forward head is.  It replaces a sync / merge
>> and
>> the  trees become exactly syncronized via a shared head.   I have mixed
>> feelings about fast forward heads, but they don't hide _too_ much
>> information.
>
> The question is how hard it is to do a reconstruction. In the current
> state automatic reconstruction is simply not possible.

You keep evading the question. What are you reconstructing, and why? What questions can you then answer with your reconstruction that you can't answer with what we already have today. You HAVE to explain what the VALUE of the end result is beyond what we already have today.

Show 6 quoted lines

>> Is there any _useful_ question you can ask where the answer
>> is lost for all time because of this.
>
> I want to see the history of _any_ repository in the order of  changes
> in the specific repository. The fast forward heads without additional
> information simply do not allow this.

Then just download their repository with the -t switch of rsync or its equal and preserve the timestamps on the files as they exist in the remote repository.

> I want to see the history of a file in the correct order. The current
> solution ends up with useless file version diffs or annotates where
> changes are shown in random order and therefor worthless.
>

What is this correct order you're talking about? The order is _given_ explicitly in the parent child relationships. There is no other order of any value, at least none you've been able to put forth.

Sean