git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: admin@inferencium.net
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Modernise .gitconfig Signing Block Name
Date: Sat, 02 Mar 2024 13:08:21 -0800	[thread overview]
Message-ID: <xmqqsf18wddm.fsf@gitster.g> (raw)
In-Reply-To: <KfyeAjLLXySd6IEKwEmOvrDqtBIhoCRPon7r8IuUIwPbUhlf8XR0CCmqP3Y5D-8hur57_SFQPqwk0xOA7p0h6xqw48ZMdNbzTBPN2hh9Ph4=@inferencium.net> (admin@inferencium.net's message of "Sat, 02 Mar 2024 20:01:26 +0000")

admin@inferencium.net writes:

> For backwards compatibility, `[gpg]` can also be allowed as an
> alias for the new name. The default could also be `format = gpg`,
> as it's still the most widely-used signing method.

Sounds good.  Patches welcome.

Thanks.

      reply	other threads:[~2024-03-02 21:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-02 20:01 Modernise .gitconfig Signing Block Name admin
2024-03-02 21:08 ` Junio C Hamano [this message]

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=xmqqsf18wddm.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=admin@inferencium.net \
    --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).