From: Junio C Hamano <gitster@pobox•com>
To: Brandon Williams <bmwill@google•com>
Cc: git@vger•kernel.org, sbeller@google•com
Subject: Re: [PATCH] submodules: update documentaion for submodule branches
Date: Wed, 19 Oct 2016 15:43:20 -0700 [thread overview]
Message-ID: <xmqqzim0hsdz.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <xmqqmvi0j9rv.fsf@gitster.mtv.corp.google.com> (Junio C. Hamano's message of "Wed, 19 Oct 2016 14:42:28 -0700")
Junio C Hamano <gitster@pobox•com> writes:
> Brandon Williams <bmwill@google•com> writes:
>
>> Update the documentaion for the the special value `.` to indicate that
>> it signifies that the tracking branch in the submodule should be the
>> same as the current branch in the superproject.
>
> Thanks. Will typofix while extending with info supplied by Stefan
> like so:
Ugh. Should have proof-read before sending it out.
> 4d7bc52b17 ("submodule update: allow '.' for branch value",
> 2016-08-03) adopted from Gerrit a feature to set "." as a special
> value of "submodule.<name>.branch" in .gitmodules file to indicate
> that it signifies that the tracking branch in the submodule should
> be the same as the current branch in the superproject.
... in .gitmodules file to indicate that the tracking branch in
the submodule should be ...
"to indicate that it signifies that" was overly redundant.
next prev parent reply other threads:[~2016-10-19 22:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-19 20:42 [PATCH] submodules: update documentaion for submodule branches Brandon Williams
2016-10-19 20:45 ` Stefan Beller
2016-10-19 21:42 ` Junio C Hamano
2016-10-19 22:43 ` Junio C Hamano [this message]
2016-10-19 23:01 ` Brandon Williams
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=xmqqzim0hsdz.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox$(echo .)com \
--cc=bmwill@google$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=sbeller@google$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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