From: Christian Jaeger <christian@jaeger.mine.nu>
To: Git Mailing List <git@vger.kernel.org>
Subject: git tag -s: TAG_EDITMSG should not be deleted upon failures
Date: Wed, 03 Dec 2008 16:53:24 +0100 [thread overview]
Message-ID: <4936AB74.3090901@jaeger.mine.nu> (raw)
Before I've now set my default signing key id in my ~/.gitconfig, I've
run at least half a dozen times into the case where I'm running "git tag
-s $tagname", carefully preparing a tag message, saving the file &
exiting from the editor, only to be greeted with an error message that
no key could be found for my (deliberately host-specific) email address,
and my message gone. If it would keep the TAG_EDITMSG file (like git
commit seems to be doing with COMMIT_EDITMSG anyway), I could rescue the
message from there. I relentlessly assume that this small change would
also make a handful of other people happier.
Christian.
next reply other threads:[~2008-12-03 15:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-03 15:53 Christian Jaeger [this message]
2008-12-06 19:40 ` git tag -s: TAG_EDITMSG should not be deleted upon failures Jeff King
2008-12-06 19:42 ` Jeff King
2008-12-06 21:28 ` Junio C Hamano
2008-12-06 21:54 ` Jeff King
2008-12-06 23:00 ` Junio C Hamano
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=4936AB74.3090901@jaeger.mine.nu \
--to=christian@jaeger.mine.nu \
--cc=git@vger.kernel.org \
/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).