From: skillzero@gmail.com
To: git@vger.kernel.org
Subject: Why do git submodules require manual checkouts and commits?
Date: Thu, 15 May 2008 21:16:23 -0700 [thread overview]
Message-ID: <2729632a0805152116o3c998324xb401674207dd2e1e@mail.gmail.com> (raw)
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)?
next reply other threads:[~2008-05-16 4:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-16 4:16 skillzero [this message]
2008-05-16 10:17 ` Why do git submodules require manual checkouts and commits? Johannes Schindelin
2008-05-16 13:43 ` Avery Pennarun
2008-05-16 13:58 ` Johannes Schindelin
2008-05-16 14:12 ` Avery Pennarun
2008-05-16 14:24 ` Johannes Schindelin
2008-05-16 14:44 ` Avery Pennarun
2008-05-16 14:58 ` Lars Hjemli
2008-05-19 4:38 ` skillzero
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2729632a0805152116o3c998324xb401674207dd2e1e@mail.gmail.com \
--to=skillzero@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).