From: Stefan Beller <sbeller@google.com>
To: David Turner <novalis@novalis.org>
Cc: Junio C Hamano <gitster@pobox.com>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: [PATCH] submodule update --init: displays correct path from submodule
Date: Fri, 6 Jan 2017 17:01:15 -0800 [thread overview]
Message-ID: <CAGZ79kZDebuqV7q-bcqG-g7E8hBq3RMa0jSDgD1Ho5BN0sByog@mail.gmail.com> (raw)
In-Reply-To: <1483750501.31165.9.camel@frank>
On Fri, Jan 6, 2017 at 4:55 PM, David Turner <novalis@novalis.org> wrote:
> (for the test)
> Signed-off-by: David Turner <dturner@twosigma.com>
>
> TIL: super-prefix!
yeah that was introduced recently for prefixes from "outside the repository"
e.g. a superproject, its first user is grep --recurse-submodules.
Also I realize I have set diff.context to 15 as I was experimenting
with it earlier,
and forgot to turn it off. So a lot of context in the diff for the patch.
Thanks for the bug report,
Stefan
prev parent reply other threads:[~2017-01-07 1:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-07 0:19 [PATCH] submodule update --init: displays correct path from submodule Stefan Beller
2017-01-07 0:55 ` David Turner
2017-01-07 1:01 ` Stefan Beller [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=CAGZ79kZDebuqV7q-bcqG-g7E8hBq3RMa0jSDgD1Ho5BN0sByog@mail.gmail.com \
--to=sbeller@google.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=novalis@novalis.org \
/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).