Re: git-submodule getting submodules from the parent repository
- From
Avery Pennarun <apenwarr@gmail.com>
- Date
- Mar 30, 2008, 23:03 UTC
- Message-ID
- <32541b130803301603u65d1b6b6ladac0f6200433e5f@mail.gmail.com>
- In-Reply-To
- <C38585A9-F09C-4A5B-8E72-6F3127DB2BB9@orakel.ntnu.no>
On Sun, Mar 30, 2008 at 3:50 PM, Eyvind Bernhardsen <eyvind-git@orakel.ntnu.no> wrote:
> Pushing to a branch works except that I couldn't figure out what to do > if the push doesn't succeed, ie, the branch has advanced on the remote > end. That's a problem if more than one module references the > submodule or there are multiple branches in the main module.
That's easy: just error out in that case. If the current system would just error out when I screwed up, I'd at least be able to deal with it. Right now I silently create un-check-outable parent repositories because I failed silently to upload my latest checkins to the child repository.
> True :) I still have no idea how to figure out which submodules are > dirty, though. Solving that will enable a safe "submodule update", > which I think is more important than "submodule push".
What is unsafe about "submodule update"?
Thanks,
Avery