From: Jake Goulding <goulding@vivisimo.com>
Date: Wed, 04 Feb 2009 14:16:44 GMT
Subject: Re: [RFC PATCH 1/1] git-tag: Add --regex option
Message-ID: <4989A34C.4080104@vivisimo.com>
In-Reply-To: <7vljsm3aow.fsf@gitster.siamese.dyndns.org>


Junio C Hamano wrote:
> Jake Goulding <goulding@vivisimo.com> writes:
> 
>> Allows the tag pattern to be expressed as a regular expression.
> 
> We use shell globs for refname throughout the system (not just tags).  Why
> is this a good thing, other than "because we can"?
> 

I'll give the particular use-case that we are using it for:

In preparation for a release, we have a nightly tagging/building
process. We start by tagging something as 1.0.0-build1. We then do that
series for a while, then decide it is time to shift to a more thorough
QA cycle. We branch a QA branch, then start tagging at 1.0-0-rc1.
Eventually, a rc passes all QA tests and we tag that rc again as 1.0-0.

Thus, our tags look like something of the form:

1.0.0-build1
1.0.0-rc1
1.0.0

As we fix bugs, a hook automatically adds the commit hash is as a
comment to the appropriate bugzilla bug.

We whipped up a dinky little web application that takes a hash and a
branch, and shows which tags contain that particular hash (which is the
reason for my previous commit for --contains support in git tag). We
hacked bugzilla to match on git hashes, and provide a link to this webapp.

I wanted to be able to limit the search space to (builds, rcs,
releases), but globs don't allow that amount of flexibility.

Is that a complete enough description for a rational use-case?

-Jake