From: Stefan Beller <sbeller@google.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Brandon Williams <bmwill@google.com>, Jeff King <peff@peff.net>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: [PATCHv6 2/2] pathspec: give better message for submodule related pathspec error
Date: Mon, 9 Jan 2017 12:03:59 -0800 [thread overview]
Message-ID: <CAGZ79kbkTf5mT39p6mznGuCwptdVx7hc8N8P=mKo4aoV2=-JVw@mail.gmail.com> (raw)
In-Reply-To: <xmqqbmvhyn1m.fsf@gitster.mtv.corp.google.com>
On Sun, Jan 8, 2017 at 6:39 PM, Junio C Hamano <gitster@pobox.com> wrote:
> For future reference, do not bury a useful fix behind unproven new
> things. The main purpose of this two-patch series is this change,
> and it does not have to wait for the change to allow test_commit to
> notice "-C" you have in another series.
noted.
The bug fixed here doesn't need to be fast-tracked IMO, because
of its history. (It's well documented on the web already)
I think this series can wait until the
"test_commit -C" is available.
In a reroll I'll drop the dependency then.
prev parent reply other threads:[~2017-01-09 20:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-05 19:29 [PATCHv6 0/2] pathspec: give better message for submodule related pathspec error Stefan Beller
2017-01-05 19:29 ` [PATCHv6 1/2] submodule tests: don't use itself as a submodule Stefan Beller
2017-01-09 2:33 ` Junio C Hamano
2017-01-09 20:10 ` Stefan Beller
2017-01-05 19:29 ` [PATCHv6 2/2] pathspec: give better message for submodule related pathspec error Stefan Beller
2017-01-09 2:39 ` Junio C Hamano
2017-01-09 20:03 ` 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
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 \
--in-reply-to='CAGZ79kbkTf5mT39p6mznGuCwptdVx7hc8N8P=mKo4aoV2=-JVw@mail.gmail.com' \
--to=sbeller@google.com \
--cc=bmwill@google.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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).