From: Brandon Williams <bmwill@google.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, sbeller@google.com
Subject: Re: [PATCH] submodules: update documentaion for submodule branches
Date: Wed, 19 Oct 2016 16:01:30 -0700 [thread overview]
Message-ID: <20161019230130.GA21768@google.com> (raw)
In-Reply-To: <xmqqzim0hsdz.fsf@gitster.mtv.corp.google.com>
On 10/19, Junio C Hamano wrote:
> 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.
Sorry that seems to have stemed from my poor commit message.
--
Brandon Williams
prev parent reply other threads:[~2016-10-19 23:01 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
2016-10-19 23:01 ` Brandon Williams [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=20161019230130.GA21768@google.com \
--to=bmwill@google.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=sbeller@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.