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

Re: git-submodule getting submodules from the parent repository

From
Avery Pennarun <apenwarr@gmail.com>
Date
Mar 31, 2008, 21:24 UTC
Message-ID
<32541b130803311424h339a30e6g4328ea27045c681d@mail.gmail.com>
In-Reply-To
<47F08343.20209@viscovery.net>
On Mon, Mar 31, 2008 at 2:22 AM, Johannes Sixt <j.sixt@viscovery.net> wrote:
Show 17 quoted lines
> Avery Pennarun schrieb:
> > It's a  pain to check out / mirror / check in / push.  git-submodule
>  > doesn't even init automatically when you check out A, so you have to
>  > run it yourself.  The relative paths of A, B, and C on your mirror
>  > have to be the same as upstream.  You can't make a local mirror of A
>  > without mirroring B and C.  B and C start out with a disconnected
>  > HEAD, so if you check in, it goes nowhere, and then when you push,
>  > nothing happens, and if you're unlucky enough to pull someone else's
>  > update to A and then "git-submodule update", it forgets your changes
>  > entirely.  When you check in to C, you then have to check in to B, and
>  > then to A, all by hand; and when you git-pull, you'd better to C, then
>  > B, then A, or risk having A try to check out a revision from B that
>  > you haven't pulled, etc.
>
>  Would a "recurse" sub-command help your workflow?
>
>  http://thread.gmane.org/gmane.comp.version-control.git/69834

Well, typing "git submodule recurse push" or something would allow me to lose the same data without typing quite as much, so strictly speaking I guess it would be an improvement :)

I'd like it even more if "git push" actually somehow refused to push at all if I forgot to push in the submodules.

Have fun,
Avery
Previous: Johannes Sixt
Message 20 of 20 in “git-submodule getting submodules from the parent repository”
  1. Avery PennarunMar 29, 2008
  2. Sam VilainMar 29, 2008
  3. Eyvind BernhardsenMar 30, 2008
  4. Sam VilainMar 30, 2008
  5. Eyvind BernhardsenMar 30, 2008
  6. Sam VilainMar 30, 2008
  7. Eyvind BernhardsenMar 31, 2008
  8. Avery PennarunMar 30, 2008
  9. Eyvind BernhardsenMar 31, 2008
  10. Avery PennarunMar 31, 2008
  11. Sam VilainApr 1, 2008
  12. Avery PennarunApr 1, 2008
  13. Junio C HamanoApr 2, 2008
  14. Avery PennarunApr 2, 2008
  15. Sam VilainApr 2, 2008
  16. Junio C HamanoApr 2, 2008
  17. Avery PennarunMar 30, 2008
  18. Sam VilainApr 1, 2008
  19. Johannes SixtMar 31, 2008
  20. Avery PennarunMar 31, 2008

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.