From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Jeff King <peff@peff.net>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: [RFC/PATCH] recognize pathspec magic without "--" disambiguation
Date: Sat, 27 May 2017 11:54:07 +0200 [thread overview]
Message-ID: <CACBZZX6K7ppVB0qYah76_+pjTKjsco3rHT0xRyKtF2H1dS4k_w@mail.gmail.com> (raw)
In-Reply-To: <20170525152739.t63dbsq2dojy2y2h@sigill.intra.peff.net>
On Thu, May 25, 2017 at 5:27 PM, Jeff King <peff@peff.net> wrote:
> git log :/foo.*bar
Another option would be to deprecate the :/rx syntax over some period
in favor of ^{/rx}.
I think it's too ugly to live, and really useless. It's equivalent to
"--grep=<rx> --all". Does anyone use this and not really mean to use
^{/rx}? E.g. "git show :/fix" might show a fix on some unrelated
branch you recently rebased.
> will be treated as a pathspec (if it doesn't match a
> commit message) due to the wildcard matching in
> 28fcc0b71.
So it might DWYM after hanging there looking at your entire history
for a commit message matching foo.*bar? And if you make such a commit
it'll start meaning something else entirely?
next prev parent reply other threads:[~2017-05-27 9:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-25 15:27 [RFC/PATCH] recognize pathspec magic without "--" disambiguation Jeff King
2017-05-26 2:13 ` Junio C Hamano
2017-05-26 13:24 ` Jeff King
2017-05-26 19:06 ` [PATCH 0/6] make "^:foo" work without disambiguating "--" Jeff King
2017-05-26 19:06 ` [PATCH 1/6] t4208: add check for ":/" without matching file Jeff King
2017-05-26 19:07 ` [PATCH 2/6] check_filename(): refactor ":/" handling Jeff King
2017-05-26 19:07 ` [PATCH 3/6] check_filename(): use skip_prefix Jeff King
2017-05-26 19:08 ` [PATCH 4/6] check_filename(): handle ":^" path magic Jeff King
2017-05-26 19:10 ` [PATCH 5/6] verify_filename(): treat ":(magic)" as a pathspec Jeff King
2017-05-26 19:10 ` [PATCH 6/6] verify_filename(): flip order of checks Jeff King
2017-05-27 9:54 ` Ævar Arnfjörð Bjarmason [this message]
2017-05-27 20:39 ` [RFC/PATCH] recognize pathspec magic without "--" disambiguation Jeff King
2017-05-28 0:04 ` 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
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=CACBZZX6K7ppVB0qYah76_+pjTKjsco3rHT0xRyKtF2H1dS4k_w@mail.gmail.com \
--to=avarab@gmail.com \
--cc=git@vger.kernel.org \
--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).