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

Re: multiple branches or multiple repositories

From
Jeff King <peff@peff.net>
Date
Nov 3, 2006, 16:01 UTC
Message-ID
<20061103160115.GA27895@coredump.intra.peff.net>
In-Reply-To
<eie7ae$ib6$1@sea.gmane.org>
On Fri, Nov 03, 2006 at 02:51:30AM +0100, Han-Wen Nienhuys wrote:
Show 7 quoted lines
>  - for each module, create a separate git repository.  Inside the 
> repository, each subproject has its own branching
> 
>  - put each module as a separate branch in a shared repository.
> 
> I think the first option is the most natural one, but are there any 
> issues, besides namespace pollution to the second option?

I don't believe there is currently an option to git-clone to grab only a single branch, so cloners in the second case would end up having to get _all_ modules (though such an option would probably not be hard to implement).

The plus side is that a single 'fetch' would grab updates for all modules (with only a single connection to the server).

Previous: Linus Torvalds
Message 4 of 4 in “multiple branches or multiple repositories”
  1. Han-Wen NienhuysNov 3, 2006
  2. Junio C HamanoNov 3, 2006
  3. Linus TorvaldsNov 3, 2006
  4. Jeff KingNov 3, 2006

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.