git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [OT] mutually supervised developers

From
Linus Torvalds <torvalds@osdl.org>
Date
Jun 11, 2005, 23:14 UTC
Message-ID
<Pine.LNX.4.58.0506111612140.2286@ppc970.osdl.org>
In-Reply-To
<7vy89gsiak.fsf@assigned-by-dhcp.cox.net>
On Sat, 11 Jun 2005, Junio C Hamano wrote:
Show 16 quoted lines
> 
> I am wondering if the world would be a better place if this
> fictitious project sets up public repositories in the following
> way:
> 
>  (1) each developer's own repository is public;
> 
>  (2) these developers pull from each other "only good stuff",
>      rejecting things he or she feels questionable.  Let's
>      forget that current GIT does not give a direct support for
>      cherrypicking for now.
> 
>  (3) the public canonical repository is updated to contain the
>      intersection (_not_ union) of these developer repositories.
>      Let's also forget that current GIT does not have automated
>      way to do such a thing.
I've thought about it, but one problem ends up being the history.

Even if both developers have the same patches, they may not have gotten them in the same order, which means that it's basically impossible to retain history when doign an intersection. Unions are different - we can just add the new history when we create a union.

> Would people find something like this arrangement workable and
> worthwhile?
If you can explain how it would actually work.. 
		Linus
Previous: Junio C HamanoNext: David Roundy
Message 2 of 3 in “[OT] mutually supervised developers”
  1. Junio C HamanoJun 11, 2005
  2. Linus TorvaldsJun 11, 2005
  3. David RoundyJun 12, 2005

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.