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

From: Thomas Gleixner <tglx@linutronix.de>
Date: May 11, 2005, 22:48 UTC
Message-ID: <1115851718.22180.153.camel@tglx>
In-Reply-To: <2853.10.10.10.24.1115850996.squirrel@linux1>

On Wed, 2005-05-11 at 18:36 -0400, Sean wrote:

Show 8 quoted lines

> On Wed, May 11, 2005 6:30 pm, Thomas Gleixner said:
> 
> > At this point it is completely irrelevant if you pulled from A or B. The
> > originator of Head A is A forever.
> 
> But who cares what repository was used to create the object?   You can't
> talk to a repository.   What you want to know is who created the object,
> and Author/Committer completely solves that problem.

Maybe you have missed the point, where one Committer holds more than one repository. See davem/net-2.6 and davem/sparc-2.6. Not to talk of Russell King's and Greg's multiple repositories. The Author is irrelevant, because one Author sends patches to more than one maintainer. Author _cannot_ be a source of tracking information. If you want to do heuristic guesses on Author/Committer pairs, then you make the situation more complex than it is already.

> If on the otherhand you're trying to reliably track the chain-of-command
> that landed the object in your repository, your patch falls short.

As I said before it is completely irrelevant whether fast forward was pulled into C directly from A or from B.

Whats the relevant content of getting the same thing from A or B ?

If you want to do this, you break the fast forward mechanism and reinvent the pull ping-pong which is avoided by the fast forwards.

tglx