From: Junio C Hamano <gitster@pobox•com>
To: Robert Dailey <rcdailey.lists@gmail•com>
Cc: Git <git@vger•kernel.org>
Subject: Re: Proposal for pruning tags
Date: Fri, 06 Jun 2014 10:18:40 -0700 [thread overview]
Message-ID: <xmqqa99qq7m7.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <CAHd499A2c09am7iFU9st-9MiNqBh_2SSyMqm+54cKL+Yq27fWA@mail.gmail.com> (Robert Dailey's message of "Fri, 6 Jun 2014 08:54:30 -0500")
Robert Dailey <rcdailey.lists@gmail•com> writes:
> ... Having git clean up tags
> automatically would really help with this, even though you may not
> feel it's the responsibility of Git. It's more of a usability issue,
I agree with "Having ... help with this". I did not say at all that
it is not something Git should and can try to help. I also agree
with it is a usability issue.
The thing is, the word "automatically" in your "clean up tags
automatically" is still too loose a definition of what we want, and
we cannot come up with a way to help users without tightening that
looseness. As you said, you are looking for something that can tell
between two kinds of tags that locally exist without having a copy
at the 'origin':
- ones that you do not want to keep
- others that you haven't pushed to (or forgot to push to) 'origin'
without giving the users a way to help Git to tell these two kinds
apart and only remove the former.
So...
next prev parent reply other threads:[~2014-06-06 17:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-05 14:51 Proposal for pruning tags Robert Dailey
2014-06-05 20:50 ` Junio C Hamano
2014-06-06 13:54 ` Robert Dailey
2014-06-06 17:18 ` Junio C Hamano [this message]
2014-06-11 9:25 ` Michael Haggerty
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=xmqqa99qq7m7.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=rcdailey.lists@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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