On Thu, Dec 5, 2013 at 2:54 PM, Jens Lehmann <jens.lehm...@web.de> wrote:
> Am 05.12.2013 20:27, schrieb Martin Langhoff:
>> On Thu, Dec 5, 2013 at 2:18 PM, Jens Lehmann <jens.lehm...@web.de> wrote:
>>> Without knowing more I can't think of a reason why submodules should
>>> not suit your use case (but you'd have to script branching and tagging
>>> yourself until these commands learn to recurse into submodules too).
>> The submodules feature is way too fiddly and has abundant gotchas.
> Care to explain what bothers you the most? Being one of the people
> improving submodules I'm really interested in hearing more about that.
Very glad to hear submodules is getting TLC! I have other scenarios at
$dayjob where I may need submodules, so happy happy.
I may be unaware of recent improvements, here's my (perhaps outdated) list
- git clone does not clone existing submodules by default. An ideal
workflow assumes that the user wants a fully usable checkout.
- git pull does not fetch&update all submodules (assuming a trivial
"tracking repos" scenario)
- git push does not warn if you forgot to push commits in the submodule
there's possibly a few others that I've forgotten. The main issue is
that things that are conceptually simple (clone, git pull with no
local changes) are very fiddly. Our new developers, testers and
support folks hurt themselves with it plenty.
I don't mind complex scenarios being complex to handle. If you hit a
nasty merge conflict in your submodule, and that's gnarly to resolve,
that's not a showstopper.
While writing this email, I reviewed Documentation/git-submodule.txt
in git master, and it does seem to have grown some new options. I
wonder if there is a tutorial with an example workflow anywhere
showing the current level of usability. My hope is actually for some
bits of automagic default behaviors to help things along (rather than
Early git was very pedantic, and over time it learned some DWIMery.
You're giving me hope that similar smarts might have grown in around
submodule support ...
- ask interesting questions
- don't get distracted with shiny stuff - working code first
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html