From: Han-Wen Nienhuys <hanwen@xs4all.nl>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: git tag: don't complain of empty messages
Date: Thu, 16 Nov 2006 01:14:56 +0100 [thread overview]
Message-ID: <455BAD80.1080108@xs4all.nl> (raw)
In-Reply-To: <7v64dgo9gj.fsf@assigned-by-dhcp.cox.net>
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
--
next prev parent reply other threads:[~2006-11-16 0:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-15 15:34 git tag: don't complain of empty messages Han-Wen Nienhuys
2006-11-15 16:02 ` Johannes Schindelin
2006-11-15 16:05 ` Han-Wen Nienhuys
2006-11-15 16:19 ` Johannes Schindelin
2006-11-15 18:23 ` Junio C Hamano
2006-11-16 0:14 ` Han-Wen Nienhuys [this message]
2006-11-16 0:38 ` Jakub Narebski
2006-11-16 1:27 ` Han-Wen Nienhuys
2006-11-26 16:42 ` Han-Wen Nienhuys
2006-11-26 16:46 ` Han-Wen Nienhuys
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=455BAD80.1080108@xs4all.nl \
--to=hanwen@xs4all.nl \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).