From: Tom Jones <tom@oxix.org>
To: Jeff King <peff@peff.net>
Cc: Stefan Beller <sbeller@google.com>,
Matthieu Moy <Matthieu.Moy@imag.fr>,
"git@vger.kernel.org" <git@vger.kernel.org>,
Junio C Hamano <gitster@pobox.com>
Subject: Re: [Request for Documentation] Differentiate signed (commits/tags/pushes)
Date: Tue, 7 Mar 2017 10:45:50 +0100 [thread overview]
Message-ID: <20170307094549.GB23052@dufour.oxix.org> (raw)
In-Reply-To: <20170307092353.ibirvitsxhzn3apz@sigill.intra.peff.net>
We use git to manage a config management repository for some
servers. We have tens of signed commits a day; all get deployed.
The logic on each host is roughly "is signed by sysadmin key and
is more recent than currently-deployed version".
Also, what is all this about "GPG"? The protocol is OpenPGP. A
particular implementation is GnuPG / gpg. It is completely mad
that this implementation detail is in the interface specs for git,
such as --gpg-sign for git-commit(1).
It is an indictment of a lack of appreciation of the relationship
between interfaces and implementations, and the importance of
proper treatment thereof.
If Bob creates Bob's git compatible program, and he happens to use
Bob's OpenPGP implementation, his compatible option for git-commit(1)
still has to be called "--gpg-sign". Madness.
Tom.
next prev parent reply other threads:[~2017-03-07 14:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-06 19:59 [Request for Documentation] Differentiate signed (commits/tags/pushes) Stefan Beller
2017-03-06 22:13 ` Junio C Hamano
2017-03-06 22:52 ` Stefan Beller
2017-03-07 0:08 ` Junio C Hamano
2017-03-07 0:58 ` Stefan Beller
2017-03-06 23:03 ` Junio C Hamano
2017-03-06 23:59 ` Jakub Narębski
2017-03-07 0:16 ` Junio C Hamano
2017-03-07 7:16 ` Matthieu Moy
2017-03-07 9:23 ` Jeff King
2017-03-07 9:45 ` Tom Jones [this message]
2017-03-07 22:19 ` Stefan Beller
2017-03-08 5:41 ` Jeff King
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=20170307094549.GB23052@dufour.oxix.org \
--to=tom@oxix.org \
--cc=Matthieu.Moy@imag.fr \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
--cc=sbeller@google.com \
/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).