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

From: Jan Harkes <jaharkes@cs.cmu.edu>
Date: May 12, 2005, 13:29 UTC
Message-ID: <20050512132922.GB20785@delft.aura.cs.cmu.edu>
In-Reply-To: <1115898230.11872.8.camel@tglx>

On Thu, May 12, 2005 at 01:43:50PM +0200, Thomas Gleixner wrote:

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.

But you can't add additional information to the fast-forward head. That would defeat the whole point of the fast-forward.

> 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.

Not random order, those changes were performed in parallel, so there is no order between them until they are merged, at which point the parent linkage defines the order. If you want to add a total ordering to them, write out a file with 'commit-id parent-id' pairs and run it through 'tsort'.

Your examples break if you consider additional merges where M syncs up a couple of times (f.i. at Rn-2) before M is merged back into R.

What you seem to want won't be fixed by adding a repoid, you need to keep a list of all the commits you have already seen and append any new ones whenever you look at the history. If you look whenever you pull or merge the list will be in the total ordering that you seem to expect for your repository. But that is a porcelain thing.

Jan