Hello,
GIT refuses to set annotated tags without a comment. I think this is a
silly restriction when the message is explicitly set to the empty string.
The attached patch should fix this; Unfortunately, I've been unable to
test it. Running the script with sh -x stops at
++exec /home/hanwen/usr/pkg/git/bin/git-sh-setup
--
Han-Wen Nienhuys - hanwen@xs4all.nl - http://www.xs4all.nl/~hanwen
Johannes Schindelin escreveu:
Hi,
On Wed, 15 Nov 2006, Han-Wen Nienhuys wrote:
quoted
GIT refuses to set annotated tags without a comment. I think this is a silly
restriction when the message is explicitly set to the empty string.
I think that this behaviour is on purpose: The tag will be identified
(like all objects in git) by its contents. The rationale: the filename
does not matter, since the tag _object_ is not identified by it. So, in
case you lose your .git/refs/tags/ directory, you can still reconstruct
the tags with "git-fsck-objects --full".
Without a message, the tag can still be identified by its name, which is
in the tag object contents.
--
Hi,
On Wed, 15 Nov 2006, Han-Wen Nienhuys wrote:
GIT refuses to set annotated tags without a comment. I think this is a silly
restriction when the message is explicitly set to the empty string.
I think that this behaviour is on purpose: The tag will be identified
(like all objects in git) by its contents. The rationale: the filename
does not matter, since the tag _object_ is not identified by it. So, in
case you lose your .git/refs/tags/ directory, you can still reconstruct
the tags with "git-fsck-objects --full".
Ciao,
Dscho
Hi,
On Wed, 15 Nov 2006, Han-Wen Nienhuys wrote:
Without a message, the tag can still be identified by its name, which is
in the tag object contents.
You are correct. Acked-by: me.
Ciao,
Dscho