From: Joel Brobecker <brobecker@adacore.com>
To: Andreas Schwab <schwab@suse.de>
Cc: gdb@sourceware.org
Subject: Re: Signed release tags
Date: Thu, 06 Feb 2014 09:39:00 -0000 [thread overview]
Message-ID: <20140206093919.GO5401@adacore.com> (raw)
In-Reply-To: <mvmmwi463wf.fsf@hawking.suse.de>
> IMHO it would be nice to have the release tag in git be GPG-signed.
> WDYT?
I suppose I could do it if has any benefit. I've never really worked
in an area where I felt that signing was really worth the trouble,
so I'm a little ignorant in that area.
I sign the release tarballs just because I have to. I've now added
my key to some keyring for people to be able to verify it. I guess
signing the tag will only make sure that I was the author of the
tag?
Anyways, no objection from me. I'll just follow whatever people
think is best.
--
Joel
next prev parent reply other threads:[~2014-02-06 9:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-06 8:28 Andreas Schwab
2014-02-06 9:39 ` Joel Brobecker [this message]
2014-05-06 1:29 ` Joel Brobecker
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=20140206093919.GO5401@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb@sourceware.org \
--cc=schwab@suse.de \
/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