From: Junio C Hamano <gitster@pobox.com>
To: "Mkrtchyan\, Tigran" <tigran.mkrtchyan@desy.de>
Cc: git <git@vger.kernel.org>, Jonathan Nieder <jrnieder@gmail.com>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>
Subject: Re: [PATCH v3] tag: add tag.gpgSign config option to force all tags be GPG-signed
Date: Wed, 05 Jun 2019 13:57:34 -0700 [thread overview]
Message-ID: <xmqqzhmvrbr5.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <xmqqblzbsquq.fsf@gitster-ct.c.googlers.com> (Junio C. Hamano's message of "Wed, 05 Jun 2019 13:46:05 -0700")
Junio C Hamano <gitster@pobox.com> writes:
> "Mkrtchyan, Tigran" <tigran.mkrtchyan@desy.de> writes:
>
>>> But more importantly, I think we should justify why this "not
>>> allowed" makes sense as the design of the feature. A plausible
>>> alternative design would simply follow the "last one wins" paradigm,
>>> ...
>> This is matter of convention.
>
> Oh, if you put it that way, it is quite clear that we should redo
> this part, as the rest of Git command line processing all pretty
> much follow "last one wins". I was mostly curious if there was any
> strong reason why this combination has to be different.
One reason why "last one wins" aka "you have a chance to correct
yourself" is so useful is because people can then use alias to
define leading options, e.g. with
[alias] myfoo = foo --option1 --option2 --option3
a user can say "git myfoo" to save typing, but in a rare occasion
where only options 2 and 3 (but not option 1) are desired, can use
"git myfoo --no-option1" to countermand it.
Unfortunately, I do not think we can use the same technique for
options that is given to the "git" potty, e.g. with
[alias] paged-status = --paginate status
you can say "git paged-status" to have your "git status" output sent
to the pager, but you cannot say "git paged-status --no-pager" to
defeat that leading option. We may want to find a way to correct
it, but it is rather low on the priority scale ;-)
next prev parent reply other threads:[~2019-06-05 20:57 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
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 [this message]
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=xmqqzhmvrbr5.fsf@gitster-ct.c.googlers.com \
--to=gitster@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).