From: Daniel Barkalow <barkalow@iabervon.org>
To: git@vger.kernel.org
Subject: Submodule idea
Date: Sat, 29 Sep 2007 15:04:50 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0709291442430.5926@iabervon.org> (raw)
I *think* that it would be a great benefit if "git submodule update" would
leave you on a branch if (a) you were on that branch before, and (b)
pulling on that branch would update it to the commit that the superproject
specifies for that submodule.
Or maybe there should be a "git submodule fetch" which fetches from the
remote, and replaces FETCH_HEAD with the superproject's index entry, and
"git submodule pull" would merge it? (With the model being that the entry
in the superproject is an additional remote that you both track and
publish to)
-Daniel
*This .sig left intentionally blank*
reply other threads:[~2007-09-29 19:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=Pine.LNX.4.64.0709291442430.5926@iabervon.org \
--to=barkalow@iabervon.org \
--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