From: Marc Branchaud <marcnarc@xiplink.com>
To: Adam Monsen <haircut@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: idea: pruning stale tags
Date: Fri, 11 Mar 2011 09:48:31 -0500 [thread overview]
Message-ID: <4D7A363F.7090206@xiplink.com> (raw)
In-Reply-To: <4D790618.9000302@gmail.com>
On 11-03-10 12:10 PM, Adam Monsen wrote:
> My idea is to add functionality to git-remote to prune stale tags
> (those which no longer exist on the remote). Add a new ui:
>
> git remote prune --tags [-n | --dry-run] <name> [<remote>]
>
> I think it is not possible to know which remote tags originated
> from, yes? That's why I suggested adding the [<remote>] parameter;
> one would be required to specify the remote to sync with if more
> than one remote is configured.
I agree with this idea, but in the context of Johan's proposed overhaul of
ref namespaces:
http://thread.gmane.org/gmane.comp.version-control.git/165799/focus=165885
M.
prev parent reply other threads:[~2011-03-11 14:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-10 17:10 idea: pruning stale tags Adam Monsen
2011-03-11 14:48 ` Marc Branchaud [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=4D7A363F.7090206@xiplink.com \
--to=marcnarc@xiplink.com \
--cc=git@vger.kernel.org \
--cc=haircut@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.