git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: 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 03:14:58 -0500	[thread overview]
Message-ID: <20110222081458.GA11825@sigill.intra.peff.net> (raw)
In-Reply-To: <7vvd0cebi6.fsf@alter.siamese.dyndns.org>

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. ;)

Yet another option that would work in my example is to use
"interesting/*" as a positive pattern. But that implies that all of the
interesting ones can be grouped in that way.

I dunno. I don't really care much either way. I would probably not be a
user of this feature myself.

> 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.

-Peff

  reply	other threads:[~2011-02-22  8:15 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 [this message]
2011-02-22 10:09         ` Jakub Narebski
2011-02-22 15:27           ` Jeff King
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=20110222081458.GA11825@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=christian.halstrick@gmail.com \
    --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).