From: Junio C Hamano <gitster@pobox.com>
To: Joel Jacobson <joel@trustly.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Add .gitconfig variable commit.gpg-sign
Date: Tue, 23 Apr 2013 07:01:51 -0700 [thread overview]
Message-ID: <7v4nexmjlc.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <7vip3em8rs.fsf@alter.siamese.dyndns.org> (Junio C. Hamano's message of "Mon, 22 Apr 2013 16:43:19 -0700")
Junio C Hamano <gitster@pobox.com> writes:
> Joel Jacobson <joel@trustly.com> writes:
>
>> Signed-off-by: Joel Jacobson <joel@trustly.com>
>> ---
>> builtin/commit.c | 4 +++-
>
> No docs? No tests?
>
> As to the design, any regular configuration variable settings must
> be overridable from the command line for a single invocation. Please
> design an escape hatch in, for somebody who has this configuration
> variable set, but does not want to sign this commit he is about to
> make.
>
> Also do we generally use dash in the configuration variable names?
> I thought the norm was section.CamelCase.
Another design issue you would need to consider before deciding to
add such a configuration is how it interacts with "git rebase -i".
The command internally runs "git commit --amend", etc. and I do not
know if _all_ users who set this configuration want to unconditionally
always re-sign all these commits.
There may be other commands that internally use "git commit" that
may be affected with such a configuration variable.
prev parent reply other threads:[~2013-04-23 14:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAASwCXf3YHmdQ_eSkShyzn5VniO=ufm3VTqV1JVOUN610bzE_A@mail.gmail.com>
2013-04-22 23:43 ` [PATCH] Add .gitconfig variable commit.gpg-sign Junio C Hamano
2013-04-23 0:00 ` Joel Jacobson
2013-04-23 11:37 ` Michael J Gruber
2013-04-23 17:53 ` Junio C Hamano
2013-04-23 17:58 ` Joel Jacobson
2013-04-23 19:25 ` Junio C Hamano
2013-04-23 19:56 ` Joel Jacobson
2013-04-24 8:53 ` Sebastian Götte
2013-04-24 9:51 ` Michael J Gruber
2013-04-24 17:30 ` [PATCH 1/1] templates: pre-push hook: check for missing GPG signatures (was: Re: [PATCH] Add .gitconfig variable commit.gpg-sign) Sebastian Götte
2013-04-24 19:54 ` [PATCH 1/1] templates: pre-push hook: check for missing GPG signatures Junio C Hamano
2013-04-25 12:19 ` [PATCH v2 0/1] " Sebastian Götte
2013-04-25 16:50 ` Junio C Hamano
[not found] ` <cover.1366890748.git.jaseg@physik-pool.tu-berlin.de>
2013-04-25 12:19 ` [PATCH v2 1/1] " Sebastian Götte
2013-04-23 14:01 ` 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=7v4nexmjlc.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=joel@trustly.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).