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

Re: After-the-fact submodule detection or creation

From
Alex Riesen <raa.lkml@gmail.com>
Date
Dec 7, 2007, 07:37 UTC
Message-ID
<20071207073728.GA2847@steel.home>
In-Reply-To
<87ir3bp5sf.fsf@graviton.dyn.troilus.org>
Michael Poole, Fri, Dec 07, 2007 04:01:04 +0100:
Show 5 quoted lines
> It seems like using the current submodule code would mean that this
> kind of import would need two passes over the foreign repository,
> rather than one if the branch could be created after the parent tree
> is initially imported.  I can live with that -- it is a rather unusual
> case -- but maybe there is a better way.)

Import the core module in a branch all by itself, and merge it in every support branch?

    Supp1: o-o-o-----o-o-o-o-o-o-o
		    /
    Core:  o-o-o-o-o
		    \
    Supp2: o-o-------o-o-o-o
Previous: Michael PooleNext: Michael Poole
Message 2 of 3 in “After-the-fact submodule detection or creation”
  1. Michael PooleDec 7, 2007
  2. Alex RiesenDec 7, 2007
  3. Michael PooleDec 7, 2007

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.