Jeff King <peff@xxxxxxxx> writes: > It sounds a lot saner to me to fix "git tag", then, to ignore certain > uninteresting bits of the tag namespace. We already do allow pattern > matching the tags shown, but: > > 1. It's an fnmatch, so I don't think there is a way to do a negative > match like "ignore everything that matches release/*". > > 2. It can only be specified on the command-line, whereas obviously you > would want this as the default for a repo when you type "git tag". > > So I think we could do something like the patch below, which allows: > > # set up some boring and interesting tags > for i in boring more-boring interesting; do > for j in one two three; do > git tag $i/$j > done > done > > # 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? 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). -- 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