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

Re: [RFC GSoC 2009: git-submodule for multiple, active developers on active trees]

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Apr 1, 2009, 00:58 UTC
Message-ID
<alpine.DEB.1.00.0904010247170.10279@pacific.mpi-cbg.de>
In-Reply-To
<526944450903311649q358d43edkf07e2e5058a9e527@mail.gmail.com>
Hi,
On Tue, 31 Mar 2009, P Baker wrote:
> I'll paraphrase to see if I understand your points:
> 
> *Moving objects from submodule .git directories into the base .git/
> directory would protect the submodules and is a good idea.
No, I did not say that.

I said that moving submodules' working directory need to protected when renaming/deleting submodules.

Even worse, I think that moving the .git/ directory into the superproject's .git/ would be at least quite a bit awkward in the nested case.

> *Moving to a .git/ file from .gitmodules should be taken off of the
> goal list (I went back and read this thread:
> http://thread.gmane.org/gmane.comp.version-control.git/78605; seemed
> to clear things up).
Can't follow links here, as I am reading this offline, so cannot comment.
> *git submodule recurse would be a good option (not as a default), if
> the remaining issues are resolved.
Definitely.
> *It would be a good idea for git submodule to work with foreign VCS,
> through Daniel's patches.

But that would not only apply to submodules, but rather all repositories, to the point that "git submodule" does not need any change.

> I appreciate the guidance, it's helping me to see that some of this work 
> has already been done, it needs to be finished and pushed into a public 
> release. As an intense user of submodules, what does it do poorly/not do 
> for your needs?

One gripe I have, but which should be rather easy to fix: "git checkout -- submodule/" does not update the index, last time I checked. (It correctly does not touch the submodule's working directory.)

Another one: The most common mistake with submodules is to commit and push the superproject, after having committed (but not pushed) in the submodule. Not sure how that could be helped.

Further, often it would come in rather handy to be able to say something like "git diff $REVISION_AS_COMMITTED_IN_THE_SUPERPROJECT" from within the submodule...

git submodule summary should output to the pager by default.

Oh, and it would not hurt performance on Windows at all if git-submodule would be finally made a builtin.

Ciao, Dscho

Previous: P BakerNext: P Baker
Message 8 of 12 in “[RFC GSoC 2009: git-submodule for multiple, active developers on active trees]”
  1. P BakerMar 25, 2009
  2. Shawn O. PearceMar 30, 2009
  3. P BakerMar 31, 2009
  4. Johannes SchindelinMar 31, 2009
  5. P BakerMar 31, 2009
  6. Johannes SchindelinMar 31, 2009
  7. P BakerMar 31, 2009
  8. Johannes SchindelinApr 1, 2009
  9. P BakerApr 1, 2009
  10. Johannes SchindelinApr 1, 2009
  11. Andreas EricssonApr 1, 2009
  12. Johannes SchindelinApr 1, 2009

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.