git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Todd Zullinger <tmz@pobox.com>
Cc: "Andrzej Ośmiałowski" <me@osmialowski.net>, git@vger.kernel.org
Subject: Re: Git uses wrong subkey for signing commits with GPG key
Date: Tue, 16 Jan 2018 10:23:27 -0800	[thread overview]
Message-ID: <xmqqlggxvf1c.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <20180113172555.GS29313@zaya.teonanacatl.net> (Todd Zullinger's message of "Sat, 13 Jan 2018 12:25:55 -0500")

Todd Zullinger <tmz@pobox.com> writes:

> Glad it helped.  The git-tag documentation points to
> git-config and the user.signingKey variable in the
> CONFIGURATION section.  The git-config documentation for
> that variable currently says:
> ...
>     so you may specify a key using any method that gpg supports.
>
> Whether that can be improved without being too verbose (or
> duplicating too much of the gpg documentation), I don't
> know.

Yeah, I personally do not want to see Git's documentation sound more
autoritative than it actually is wrt how to use software from other
people, especially given that we do not have volunteers who will
closely be keeping track of their changes in order to update our
documentation.  So "any method that gpg supports" is a good place to
stop from that point of view.  "See documentation for the version of
PGP software you use for details." is not a bad thing to add without
risking to go stale, though.


      reply	other threads:[~2018-01-16 18:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-13  0:09 Git uses wrong subkey for signing commits with GPG key Andrzej Ośmiałowski
2018-01-13  0:22 ` Todd Zullinger
2018-01-13 12:40   ` Andrzej Ośmiałowski
2018-01-13 17:25     ` Todd Zullinger
2018-01-16 18:23       ` 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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqqlggxvf1c.fsf@gitster.mtv.corp.google.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=me@osmialowski.net \
    --cc=tmz@pobox.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).