From: Jeff King <peff@peff.net>
To: Jakub Narebski <jnareb@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>,
Christian Halstrick <christian.halstrick@gmail.com>,
git <git@vger.kernel.org>
Subject: Re: How to create tags outside of refs/tags?
Date: Tue, 22 Feb 2011 10:27:23 -0500 [thread overview]
Message-ID: <20110222152723.GA23353@sigill.intra.peff.net> (raw)
In-Reply-To: <m3wrks756a.fsf@localhost.localdomain>
On Tue, Feb 22, 2011 at 02:09:14AM -0800, Jakub Narebski wrote:
> > I think changing the config name to tag.list-ignore would make it more
> > obvious what is going on. If you don't want to push certain tags, I
> > think refspecs are the way to do that, and this should be a purely local
> > display thing.
>
> You meant `tag.listIgnore`, weren't you? No hyphens in config
> variable names.
Sure.
> About refspecs: we currently do not support negative refspecs, do we?
> (IIRC there was proposal to use '!' or '-' as prefix for them). So we
> can't currently exclude refs/tags/private/* while including
> refs/tags/v*?
Yeah, I think you might be stuck enumerating the tags you want via
refspec. But I stand by my statement; if this feature is something we
want, it should be purely about listing tags. I don't want to get into
weird tag-specific config affecting the what we push. If somebody wants
negative refspecs, that can be a separate patch.
But like I said before, I am lukewarm on the patch in the first place.
-Peff
next prev parent reply other threads:[~2011-02-22 15:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-21 17:21 How to create tags outside of refs/tags? Christian Halstrick
2011-02-21 17:48 ` Jay Soffian
2011-02-21 23:52 ` Junio C Hamano
2011-02-22 6:17 ` Christian Halstrick
2011-02-22 8:03 ` Jeff King
2011-02-22 8:09 ` Junio C Hamano
2011-02-22 8:14 ` Jeff King
2011-02-22 10:09 ` Jakub Narebski
2011-02-22 15:27 ` Jeff King [this message]
2011-02-22 16:21 ` Christian Halstrick
2011-02-22 18:38 ` Junio C Hamano
2011-02-22 22:08 ` Christian Halstrick
2011-02-23 12:42 ` Michael J Gruber
2011-02-23 13:45 ` Christian Halstrick
2011-02-23 16:36 ` Enrico Weigelt
2011-02-22 15:06 ` Jay Soffian
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=20110222152723.GA23353@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=christian.halstrick@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jnareb@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 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).