From: Ryan Lortie <desrt@desrt.ca>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, Chris Packham <judge.packham@gmail.com>
Subject: Re: git submodule: update=!command
Date: Tue, 17 Mar 2015 16:59:49 -0400 [thread overview]
Message-ID: <1426625989.1809668.241718517.07249CD6@webmail.messagingengine.com> (raw)
In-Reply-To: <xmqqy4mvmjs9.fsf@gitster.dls.corp.google.com>
On Tue, Mar 17, 2015, at 16:49, Junio C Hamano wrote:
> With more recent versions of Git, namely, the versions after
> 30a52c1d (Merge branch 'ms/submodule-update-config-doc' into maint,
> 2015-03-13), the documentation pages already have updated
> descriptions around this area.
sigh.
That's what I get for forgetting to type 'git pull' before writing a
patch.
Sorry for the noise!
Cheers
next prev parent reply other threads:[~2015-03-17 21:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-17 19:28 git submodule: update=!command Ryan Lortie
2015-03-17 19:50 ` Jeff King
2015-03-17 20:48 ` Ryan Lortie
2015-03-18 7:38 ` Chris Packham
2015-03-17 20:49 ` Junio C Hamano
2015-03-17 20:59 ` Ryan Lortie [this message]
2015-03-17 21:05 ` Junio C Hamano
2015-03-17 21:11 ` Ryan Lortie
2015-03-18 7:43 ` Chris Packham
2015-03-18 7:45 ` Chris Packham
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=1426625989.1809668.241718517.07249CD6@webmail.messagingengine.com \
--to=desrt@desrt.ca \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=judge.packham@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).