From: Eric Chamberland <Eric.Chamberland@giref.ulaval.ca>
To: Junio C Hamano <gitster@pobox.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: [feature request] 2) Remove many tags at once and 1) Prune tags on old-branch-before-rebase
Date: Fri, 08 Mar 2013 14:37:21 -0500 [thread overview]
Message-ID: <513A3DF1.7020009@giref.ulaval.ca> (raw)
In-Reply-To: <7v38w6lr8n.fsf@alter.siamese.dyndns.org>
Hi Junio,
On 03/07/2013 06:33 PM, Junio C Hamano wrote:
> Eric Chamberland <Eric.Chamberland@giref.ulaval.ca> writes:
>
> What you want is a way to compute, given a set of tags (or refs in
> general) and a set of branches (or another set of refs in general),
> find the ones in the former that none of the latter can reach. With
> that, you can drive "git tag -d $(that way)".
>
Yes, this is *exactly* what I want...
> In other words, the feature does not belong to "git tag" command.
>
>> 2) git tag -d "TOKEN*"
>
> Again, not interesting. You already have:
>
> git for-each-ref --format='%(refname:short)' refs/tags/TOKEN\* |
> xargs -r git tag -d
>
I don't agree here for one reason:
git tag -l "TOKEN*"
already exists and works very well...
So why is it not interesting to have:
git tag -d "TOKEN*"
?
We can also write:
git tag -d `git tag -l "TOKEN*"`
but a simple addition to "-d" feature looks like a receivable behavior
here, no?
Thanks,
Eric
prev parent reply other threads:[~2013-03-08 19:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-07 22:01 [feature request] 2) Remove many tags at once and 1) Prune tags on old-branch-before-rebase Eric Chamberland
2013-03-07 23:33 ` Junio C Hamano
2013-03-08 19:37 ` Eric Chamberland [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=513A3DF1.7020009@giref.ulaval.ca \
--to=eric.chamberland@giref.ulaval.ca \
--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).