From: Jeff King <peff@peff.net>
To: Eric Sunshine <sunshine@sunshineco.com>
Cc: Junio C Hamano <gitster@pobox.com>, Pete Harlan <pgit@tento.net>,
Karthik Nayak <karthik.188@gmail.com>,
Git List <git@vger.kernel.org>
Subject: Re: [PATCH] tag: do not show ambiguous tag names as "tags/foo"
Date: Mon, 25 Jan 2016 04:56:29 -0500 [thread overview]
Message-ID: <20160125095629.GB24452@sigill.intra.peff.net> (raw)
In-Reply-To: <CAPig+cTq0j0ss=qw9Dx8-PqFA5WJwP0mpvoO+5=NXtOt2EUNww@mail.gmail.com>
On Sun, Jan 24, 2016 at 06:39:05PM -0500, Eric Sunshine wrote:
> > Yeah, "strip=2" would also get the job done, and extends more naturally
> > to the branch case.
> >
> > To be honest, I cannot imagine anybody using anything _but_ strip=2, but
> > maybe there are special cases, like:
> >
> > git for-each-ref --format='%(refname:strip=3)' refs/heads/jk/
> >
> > to get my list of topics, sans initials.
>
> What if the option was named ":stripprefix=" in its most general form:
>
> %(refname:stripprefix=refs/tags/)
>
> with plain:
>
> %(refname:stripprefix)
>
> shorthand for ":stripprefix=refs/*/" or something?
That would work, though I was really hoping not to get into something as
complicated as globbing. I'm not sure it really buys us that much here.
-Peff
next prev parent reply other threads:[~2016-01-25 9:56 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-23 23:56 Regression? Ambiguous tags listed as "tags/<foo>" Pete Harlan
2016-01-24 7:12 ` [PATCH] tag: do not show ambiguous tag names as "tags/foo" Jeff King
2016-01-24 7:18 ` Jeff King
2016-01-24 22:19 ` Junio C Hamano
2016-01-24 22:27 ` Jeff King
2016-01-24 23:39 ` Eric Sunshine
2016-01-25 9:56 ` Jeff King [this message]
2016-01-25 2:26 ` Junio C Hamano
2016-01-25 10:01 ` Jeff King
2016-01-25 19:29 ` Karthik Nayak
2016-01-25 20:21 ` Junio C Hamano
2016-01-26 2:37 ` Jeff King
2016-01-26 3:00 ` Jeff King
2016-01-26 3:25 ` Junio C Hamano
2016-01-24 23:05 ` Jeff King
2016-01-24 23:08 ` [PATCH 1/2] t6300: use test_atom for some un-modern tests Jeff King
2016-01-24 23:08 ` [PATCH 2/2] tag: do not show ambiguous tag names as "tags/foo" Jeff King
2016-01-26 0:04 ` Junio C Hamano
2016-01-26 4:25 ` Karthik Nayak
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=20160125095629.GB24452@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=karthik.188@gmail.com \
--cc=pgit@tento.net \
--cc=sunshine@sunshineco.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).