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 -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html