Re: How to create tags outside of refs/tags?

From: Jakub Narebski <jnareb@gmail.com>
Date: Feb 22, 2011, 10:09 UTC
Message-ID: <m3wrks756a.fsf@localhost.localdomain>
In-Reply-To: <20110222081458.GA11825@sigill.intra.peff.net>

Jeff King <peff@peff.net> writes:

Show 11 quoted lines

> On Tue, Feb 22, 2011 at 12:09:37AM -0800, Junio C Hamano wrote:
> 
> > >   # tell git to ignore boring stuff
> > >   git config tag.ignore 'boring/*'
> > >   git config --add tag.ignore 'more-boring/*'
> > 
> > Hmph, isn't that what "grep -v" was invented for?
> 
> Heh. Yeah, but I think the point is that you will want to do this _every
> time_, so it saves typing. I guess you could make an alias. Or even more
> hack-ish, a custom tag.pager that filters the results. ;)

[...]

Show 10 quoted lines

> > Also it is unclear if the boring tags will or will not be propagated (or
> > should or should not be, for that matter) to outer world when you do "git
> > push --tags" with your "ignore".  Most likely some people do want to see
> > them hidden (e.g. when publishing), and some others do want to be pushed
> > (e.g. when backing the repository up).
> 
> 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.

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*?

-- 
Jakub Narebski
Poland
ShadeHawk on #git