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

From: Thomas Gleixner <tglx@linutronix.de>
Date: May 11, 2005, 23:33 UTC
Message-ID: <1115854419.22180.196.camel@tglx>
In-Reply-To: <2883.10.10.10.24.1115852463.squirrel@linux1>

On Wed, 2005-05-11 at 19:01 -0400, Sean wrote:

> Why would anyone care how many repositories Russell or Greg use?  Why does
> anyone care if Dave used his repo A, B, or C?   Aren't I still just going
> to contact him via his author email addy if I have an issue with an object
> he has added to the stream?

He? What the hell have the sparc-2.6 and net-2.6 in common except the same owner/maintainer ? Should we base the heuristics on directories and filenames ? Cool.

It is relevant for the maintainers to have information which is consistent over a repository. So the source of change _is_ relevant.

> Exactly!!!  So what is relevant of getting the same thing from Dave's A or
> B?

The relevant part is, that it _is_ relevant for Dave to know where the hell a problem was introduced.

> The only point would be to show chain of command, but you don't seem
> interested in that.

What is the chain of commands good for ? Does the chain of commands change the history information in a specific repository ?

No.

If you buy food, then it is relevant if you get it from A directly or via B. The commit and the referenced tree is immutable and does neither change the consistency nor gets uneatable.

> > 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.
> 
> Yes, I think there are other ways to avoid the ping pong too.

True, but not with a plain rsync approach

tglx