From: Junio C Hamano <gitster@pobox.com>
To: Nicolas Vigier <boklm@mars-attacks.org>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Dec 2013, #03; Thu, 12)
Date: Mon, 16 Dec 2013 09:14:15 -0800 [thread overview]
Message-ID: <xmqqy53kpvko.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <20131216123040.GZ11745@mars-attacks.org> (Nicolas Vigier's message of "Mon, 16 Dec 2013 13:30:40 +0100")
Nicolas Vigier <boklm@mars-attacks.org> writes:
> On Sun, 15 Dec 2013, Junio C Hamano wrote:
>
>> Besides, we would need at least something like this to make sure
>> that people have a way to selectively disable configured default
>> when necessary, perhaps like this.
>
> This looks like a good idea.
I said "at least" because I suspect this is far from sufficient.
When the variable is set, there is no way to say "do not bother
signing commits when stashing WIP changes", for example, no?
Scripted Porcelains that happen to use commit-tree are all affected,
while those that have been rewritten in C and internally make calls
to commit_tree() (e.g. "git merge") will not be affected by it. I
still am not convinced that this configuration variable is a good
idea in the first place, but I am not its audience, so....
next prev parent reply other threads:[~2013-12-16 17:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-13 0:57 What's cooking in git.git (Dec 2013, #03; Thu, 12) Junio C Hamano
2013-12-13 1:05 ` Duy Nguyen
2013-12-13 20:58 ` Junio C Hamano
2013-12-13 7:39 ` Torsten Bögershausen
2013-12-13 20:58 ` Junio C Hamano
2013-12-16 5:34 ` Junio C Hamano
2013-12-16 12:30 ` Nicolas Vigier
2013-12-16 17:14 ` Junio C Hamano [this message]
2013-12-16 13:55 ` [PATCH] test the commit.gpgsign config option Nicolas Vigier
2013-12-16 17:05 ` Junio C Hamano
2013-12-17 23:27 ` Junio C Hamano
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=xmqqy53kpvko.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=boklm@mars-attacks.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.