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

Re: Partial checkouts / submodules

From
SVSven Verdoolaege <skimo@kotnet.org>
Date
Nov 20, 2007, 18:42 UTC
Message-ID
<20071120184227.GB2261MdfPADPa@greensroom.kotnet.org>
In-Reply-To
<20071120181932.GA20705@pvv.org>
On Tue, Nov 20, 2007 at 07:19:33PM +0100, Finn Arne Gangstad wrote:
Show 16 quoted lines
> On Tue, Nov 20, 2007 at 06:33:50PM +0100, Sven Verdoolaege wrote:
> 
> > Just "submodule init" and "submodule update" these submodules and
> > it looks like you would get what you want...
> > 
> > > If I make a branch on submodule71, the branch is made in all submodules &
> > > the supermodule.
> > 
> > ... except this one.
> > It's not clear why you would even want this.
> 
> I'll try to boil this down to the simplest case possible. If
> submodules can do this I'll be really happy :)
> 
> Developer A makes a change in submodule1 and in submodule2
> Developer B makes a change in submodule2 and in submodule3

I'm assuming that A and B also make a commit to the supermodule incorporating their changes to the submodules (as in your original message).

> A and B don't know about eachother. They send their modifications
> somewhere (push to a shared repository with a well chosen branch name,
> for example), or send a mail "please pull from my repo" to the patch
> queue manager.

The commit A made to the superproject contains his changes to the submodule, so if someone pulls this superproject commit, she'll get the submodule changes too. (Although she may choose not to have some or all of these submodules checked out.)

Show 5 quoted lines
> Also - it would be very good if the history in the master repo would
> match the history in all developers' repositories (as the
> modifications are merged in by the patch queue manager). I.e. - you
> should see a "gif support" feature branch, see the commits on it, and
> finally the merge.
You can't change the history in git. [*1]

It's still not clear why you would want new branches to be created in other modules when you create a new branch in some module.

skimo

[*1] There are tools that allow you to create a new history based on an old history, but it will be a different history.

Previous: Finn Arne GangstadNext: Daniel Barkalow
Message 4 of 13 in “Partial checkouts / submodules”
  1. Finn Arne GangstadNov 20, 2007
  2. Sven VerdoolaegeNov 20, 2007
  3. Finn Arne GangstadNov 20, 2007
  4. Sven VerdoolaegeNov 20, 2007
  5. Daniel BarkalowNov 20, 2007
  6. Finn Arne GangstadNov 20, 2007
  7. Daniel BarkalowNov 20, 2007
  8. Jakub NarebskiNov 21, 2007
  9. Daniel BarkalowNov 20, 2007
  10. Steven GrimmNov 20, 2007
  11. Daniel BarkalowNov 20, 2007
  12. Sergei OrganovNov 20, 2007
  13. Daniel BarkalowNov 20, 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.