On Mon, Jan 31, 2011 at 03:39:41PM +0100, Jan Holesovsky <kendy@suse.cz> wrote:
Can you please do a bit of research in that regard, and summarize how we would gain from using git submobule?
To my understanding, in short:
git submodules are not like how svn externals are usually used. svn
externals usually checkout the latest revision from a trunk/branch,
while git submodules always checkout a given commit.
This means that in case one pushes to writer.git/master, then somebody
else doing a 'git submodule update' after the push will see no update.
That operation will do something only in case one updates the "submodule
link" from commit 870df5402bfadae19b9133bdce6a8db05d547925 to
47e1f5dc3b095a36e7837f2d6fc34aabed1d3997 (an example) in the build repo,
and that update will be a commit in the build repo as well.
Pro: it would be easy to bisect, since git bisect knows how to handle
submodules (currently you can just use something like g checkout
"@{2011-02-06}" and pray that you can something that builds at all)
Con: build.git has to be updated manually (it has to be decided how
frequently), ideally after every 'g push', but that would cause a lot of
"bogus" commits in build.git, which sounds ugly.
Attachment:
pgpG4KBkbaxG1.pgp
Description: PGP signature