Re: Why do git submodules require manual checkouts and commits?

Hi,

On Fri, 16 May 2008, Avery Pennarun wrote:

Think of it this way: I can commit, or not commit, my dirty Makefile at 
the same time as everything else (in a single project) with a single 
"git commit" line, depending on what I want to do.  Things like "git 
commit -a" and "git add -u" speed up the common case where I just want 
to commit everything.  But with submodules, that common case looks more 
like this:

   cd sub
   git checkout -b manual_branchname_because_there_was_no_default
   git commit -a
   git push etc.
   cd ..
   git commit -a
   git push etc.

Funny, for me it looks completely different:

$ cd sub
# work, work, work
# from time to time commit
# from time to time rebase -i to clean up some things
# test, test, test
# sometimes push

And then, every once in a while, it is

$ cd ..
$ git add submodule
$ git commit -s submodule
$ git push

That's *really* tedious, and the number of commands multiplies when you 
have more than one submodule going at once.

But hey, if you find that tedious, why did I not see a patch from you yet, 
implementing "git submodule commit-n-push"?

Ciao,
Dscho