From: Christian Couder <firstname.lastname@example.org>
To: Atharva Raykar <email@example.com>
Cc: Ben Avison <firstname.lastname@example.org>, git <email@example.com>,
Shourya Shukla <firstname.lastname@example.org>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Philippe Blain <email@example.com>
Subject: Re: Bug in git submodule update --remote
Date: Fri, 21 May 2021 20:36:23 +0200 [thread overview]
Message-ID: <CAP8UFD39ShCZRxUN7iHFUSQxO=EL18hhpbNN86SAnASHgxe6sQ@mail.gmail.com> (raw)
On Fri, May 21, 2021 at 1:47 PM Atharva Raykar <firstname.lastname@example.org> wrote:
> On 19-May-2021, at 20:11, Ben Avison <email@example.com> wrote:
> > I like that solution. Although, I should note that if the user has set
> > submodule.<name>.remote to something other than 'origin', they will need
> > to ensure that submodule.<name>.branch is also set, or they will still
> > hit the "Unable to find current <remote>/HEAD revision in submodule"
> > error that I initially stumbled on.
> > How about an implementation like the following? I introduced a new "git
> > submodule--helper" command rather than modify "print-default-remote" for
> > a couple of reasons:
First thanks for taking a look at improving git submodule and for
doing so by introducing most of the new code in submodule--helper!
> Since this would modify the behaviour of the update subcommand, I
> have decided to CC my mentors (Christian and Shourya) who are more
> qualified than me to comment on this proposal.
As commit f0a96e8d's author is Dscho (Johannes Schindelin) and as he
was helped by Philippe Blain, let me CC them too. They might know the
reasons for this behavior better than us.
next prev parent reply other threads:[~2021-05-21 18:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-14 18:11 Bug in git submodule update --remote Ben Avison
2021-05-19 10:49 ` Atharva Raykar
2021-05-19 14:41 ` Ben Avison
2021-05-21 11:47 ` Atharva Raykar
2021-05-21 18:36 ` Christian Couder [this message]
2021-05-22 19:15 ` Philippe Blain
2021-05-19 11:19 ` Atharva Raykar
2021-05-22 18:02 ` Philippe Blain
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:
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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.
Code repositories for project(s) associated with this public inbox
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 read-only IMAP folder(s) and NNTP newsgroup(s).