From: Jens Lehmann <Jens.Lehmann@web.de>
To: "Timothy M. Redaelli" <timothy.redaelli@gmail.com>, git@vger.kernel.org
Subject: Re: Force git submodule update --remote for some branches
Date: Sun, 30 Nov 2014 15:52:32 +0100 [thread overview]
Message-ID: <547B2F30.8090003@web.de> (raw)
In-Reply-To: <5478B6F1.6070200@gmail.com>
Am 28.11.2014 um 18:54 schrieb Timothy M. Redaelli:
> I have a repository with a submodule and I'd like to force git to
> checkout the LAST version of the submodule and not the stored one (like
> git submodule update --remote), but only on some branches and without
> the need to remember to add --remote every time you are on this branch.
>
> Is there any way to do it? Maybe using .gitmodules?
Not yet.
But yes, .gitmodules would be the right place to put such a
configuration as then it would be per submodule and also per
(superproject-)branch.
By the way, what do you think the output of git status and
git diff should look like when you updated a submodule to
its branch tip which differs from the commit recorded in
the superproject? Should these changes be displayed or not?
And only if the new tip is a fast-forward of the old or
always?
prev parent reply other threads:[~2014-11-30 14:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-28 17:54 Force git submodule update --remote for some branches Timothy M. Redaelli
2014-11-30 14:52 ` Jens Lehmann [this message]
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=547B2F30.8090003@web.de \
--to=jens.lehmann@web.de \
--cc=git@vger.kernel.org \
--cc=timothy.redaelli@gmail.com \
/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).