login
Header Space

 
 

Why do git submodules require manual checkouts and commits?

Score:
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: <git@...>
Date: Friday, May 16, 2008 - 12:16 am

Why do git submodules require manually committing the submodule itself
to each super repository after something in the submodule repository
changes? Is there some reason the super repository can't just "link"
to the submodules by branch name? It seems that if the .gitsubmodules
also specified the branch to use:

[submodule "libfoo"]
	path = libs/foo
	url = git://foo.com/git/libfoo.git
	branch = master

[submodule "libbar"]
	path = libs/bar
	url = git://bar.com/git/libbar.git
	branch = stable

Then a git pull (or git clone) of the super repository could also pull
in all submodules. A commit to a file in a submodule would then be
automatically reflected in the super repository (since the super
repository would always pull HEAD of that branch).

Is this difficult (or somehow undesirable)?
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
Why do git submodules require manual checkouts and commits?, , (Fri May 16, 12:16 am)
Re: Why do git submodules require manual checkouts and commi..., Johannes Schindelin, (Fri May 16, 9:58 am)
Re: Why do git submodules require manual checkouts and commi..., Johannes Schindelin, (Fri May 16, 10:24 am)
Re: Why do git submodules require manual checkouts and commi..., Johannes Schindelin, (Fri May 16, 6:17 am)
speck-geostationary