From: Todd Zullinger <tmz@pobox.com>
To: Tigran Mkrtchyan <tigran.mkrtchyan@desy.de>
Cc: git@vger.kernel.org, jrnieder@gmail.com, Johannes.Schindelin@gmx.de
Subject: Re: [PATCH v3] tag: add tag.gpgSign config option to force all tags be GPG-signed
Date: Wed, 5 Jun 2019 12:21:01 -0400 [thread overview]
Message-ID: <20190605162101.GX3654@pobox.com> (raw)
In-Reply-To: <20190605155300.26506-1-tigran.mkrtchyan@desy.de>
Hi,
Tigran Mkrtchyan wrote:
> diff --git a/Documentation/config/tag.txt b/Documentation/config/tag.txt
> index 663663bdec..675483c3c3 100644
> --- a/Documentation/config/tag.txt
> +++ b/Documentation/config/tag.txt
> @@ -8,6 +8,13 @@ tag.sort::
> linkgit:git-tag[1]. Without the "--sort=<value>" option provided, the
> value of this variable will be used as the default.
>
> +tag.gpgsign::
> + A boolean to specify whether all tags should be GPG signed.
> + Use of this option when running in an automated script can
> + result in a large number of tags being signed. It is therefore
> + convenient to use an agent to avoid typing your gpg passphrase
> + several times.
I think the variable should be camelCased, i.e. tag.gpgSign,
for consistency with other documentation.
--
Todd
next prev parent reply other threads:[~2019-06-05 16:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <60741736.3439901.1509090074292.JavaMail.zimbra@desy.de>
2019-06-04 11:43 ` config option to force all tags be GPG-signed - comeback Tigran Mkrtchyan
2019-06-04 11:43 ` [PATCH v2] tag: add tag.gpgSign config option to force all tags be GPG-signed Tigran Mkrtchyan
2019-06-04 14:33 ` Johannes Schindelin
2019-06-04 16:04 ` Mkrtchyan, Tigran
2019-06-05 15:53 ` [PATCH v3] " Tigran Mkrtchyan
2019-06-05 16:21 ` Todd Zullinger [this message]
2019-06-05 16:25 ` Junio C Hamano
2019-06-05 20:12 ` Mkrtchyan, Tigran
2019-06-05 20:46 ` Junio C Hamano
2019-06-05 20:50 ` Mkrtchyan, Tigran
2019-06-05 20:57 ` Junio C Hamano
2019-06-05 21:09 ` Mkrtchyan, Tigran
2019-06-05 21:33 ` [PATCH v4] " Tigran Mkrtchyan
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=20190605162101.GX3654@pobox.com \
--to=tmz@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
--cc=tigran.mkrtchyan@desy.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.
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).