Re: git tag: don't complain of empty messages

From: Han-Wen Nienhuys <hanwen@xs4all.nl>
Date: Nov 16, 2006, 01:27 UTC
Message-ID: <455BBE89.6070005@xs4all.nl>
In-Reply-To: <ejgbrq$o5u$1@sea.gmane.org>

Jakub Narebski escreveu:

Show 22 quoted lines

> Han-Wen Nienhuys wrote:
> 
>> Junio C Hamano escreveu:
>>> I do not have a strong objection against allowing tags without
>>> messages, but at the same time I do not see a compelling reason
>>> to allow them either.  Care to explain what workflow is helped
>>> by an empty tag?
>> the tagname usually is enough of a description, but I want the tags to 
>> end up in the object DB, eg.:
>>
>>    git tag release/2.10.0 HEAD
>>
>> now I have to use
>>
>>    git tag -m "this really sucks"  release/2.10.0 HEAD
> 
> Why not
> 
>    git tag -m "release 2.10.0" release/2.10.0 HEAD
> 
> This way you would know what tag points to even if you loose it's
> reference...

that would double, given that the tag name is already in the tag object. Currently, I have

** [lilydev@haring gub]$ cat .git/refs/tags/gubrelease-2.9.29-2 1ac5c78609a9f79787825b62c9576542eedce795

[lilydev@haring gub]$ git cat-file tag 1ac5c78609a9f79787825b62c9576542eedce795

object b75db784e3d6a9e1d2cff3f77036aaa88598b53c type commit tag gub-2.9.29-2 tagger Han-Wen Nienhuys <lilydev@haring.localdomain> 1162921716 +0100

build and upload **

'build and upload' is a polite way of saying 'this really sucks'.

-- 
  Han-Wen Nienhuys - hanwen@xs4all.nl - http://www.xs4all.nl/~hanwen