From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Nov 2013, #04; Wed, 13)
Date: Fri, 15 Nov 2013 01:48:30 -0500 [thread overview]
Message-ID: <20131115064830.GA30234@sigill.intra.peff.net> (raw)
In-Reply-To: <xmqqob5ndho5.fsf@gitster.dls.corp.google.com>
On Wed, Nov 13, 2013 at 03:07:54PM -0800, Junio C Hamano wrote:
> * nd/liteal-pathspecs (2013-10-28) 1 commit
> (merged to 'next' on 2013-11-01 at 1a91775)
> + pathspec: stop --*-pathspecs impact on internal parse_pathspec() uses
>
> Will cook in 'next'.
I think we want this to be part of v1.8.5. It is a fix for a regression
that appeared in master post-1.8.4:
$ git.v1.8.4 --literal-pathspecs blame Makefile | wc -l
2596
$ git.v1.8.5-rc2 --literal-pathspecs blame Makefile | wc -l
fatal: Makefile: pathspec magic not supported by this command: 'literal'
0
Sorry to mention it so late into the -rc cycle, but I just noticed that
the patch hadn't graduated.
-Peff
next prev parent reply other threads:[~2013-11-15 6:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-13 23:07 What's cooking in git.git (Nov 2013, #04; Wed, 13) Junio C Hamano
2013-11-15 6:48 ` Jeff King [this message]
2013-11-18 16:11 ` Junio C Hamano
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=20131115064830.GA30234@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).