From: Fabian Stelzer <fs@gigacodes.de>
To: git@vger.kernel.org
Cc: "Junio C Hamano" <gitster@pobox.com>,
"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
"Eric Sunshine" <sunshine@sunshineco.com>,
"Fabian Stelzer" <fs@gigacodes.de>
Subject: [RFC PATCH 0/2] cryptoSign flag & config
Date: Mon, 20 Dec 2021 15:09:26 +0100 [thread overview]
Message-ID: <20211220140928.1205586-1-fs@gigacodes.de> (raw)
Since git now supports multiple methods for signing objects some of the
existing flags and configuration variables can be misleading. Especially the
flags could be understood as selecting a format (--gpg-sign), which they do
not.
This series introduces the more generic name "cryptoSign". Using just "sign"
could otherwise be too easily confused with "sign-off".
For now I have only adjusted the gpg-sign flag to a single command and added
the new configuration prefix and would like to hear some feedback. If we can
agree on the naming and implementation I will of course adjust all the other
commands likewise and add some tests for the compatibility layer.
The `(commit|tag|push).gpgsign` var is still on my todo list as well.
My earlier question to the list (<xmqqzgpn50l6.fsf@gitster.g>) did not
receive much feedback so i'm sending this rfc patch.
Fabian Stelzer (2):
crypto sign: add crypto-sign alias flag
crypto sign: add cryptoSign.* config
Documentation/config/gpg.txt | 31 ++++++++++++++++++++-----------
Documentation/git-commit.txt | 15 ++++++++++-----
builtin/commit.c | 5 ++++-
gpg-interface.c | 30 ++++++++++++++++++++++--------
4 files changed, 56 insertions(+), 25 deletions(-)
--
2.33.1
next reply other threads:[~2021-12-20 14:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-20 14:09 Fabian Stelzer [this message]
2021-12-20 14:09 ` [RFC PATCH 1/2] crypto sign: add crypto-sign alias flag Fabian Stelzer
2021-12-20 21:54 ` Junio C Hamano
2021-12-21 9:37 ` Fabian Stelzer
2021-12-20 14:09 ` [RFC PATCH 2/2] crypto sign: add cryptoSign.* config Fabian Stelzer
2021-12-20 22:07 ` Eric Sunshine
2021-12-21 9:39 ` Fabian Stelzer
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=20211220140928.1205586-1-fs@gigacodes.de \
--to=fs@gigacodes.de \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=sunshine@sunshineco.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).