From: "W. Trevor King" <wking@tremily.us>
To: Git <git@vger.kernel.org>
Cc: "Junio C Hamano" <gitster@pobox.com>,
"Łukasz Gryglicki" <lukaszgryglicki@o2.pl>
Subject: Re: [PATCH v2] pull: pass --signoff/--no-signoff to "git merge"
Date: Thu, 12 Oct 2017 02:18:22 -0700 [thread overview]
Message-ID: <20171012091822.GA27403@valgrind.us> (raw)
In-Reply-To: <51d67d6d707182d4973d9961ab29358f26c4988a.1507796638.git.wking@tremily.us>
[-- Attachment #1: Type: text/plain, Size: 1468 bytes --]
On Thu, Oct 12, 2017 at 01:46:39AM -0700, W. Trevor King wrote:
> The order of options in merge-options.txt isn't clear to me, but
> I've put --signoff between --log and --stat as somewhat alphabetized
> and having an "add to the commit message" function like --log.
The order of options in merge-options.txt was intended to be by
"alphabetical groups", at least back in 7c85d274
(Documentation/merge-options.txt: order options in alphabetical
groups, 2009-10-22). I'm not quite clear on what that means. After
7c85d274 landed there were already long-option irregularities:
$ git grep -h ^-- 7c85d27 -- Documentation/merge-options.txt
--commit::
--no-commit::
--ff::
--no-ff::
--log::
--no-log::
--stat::
--no-stat::
--squash::
--no-squash::
--strategy=<strategy>::
--summary::
--no-summary::
--quiet::
--verbose::
If the order was purely alphabetical, --stat/--no-stat should have
after --squash/--no-squash, and --quiet should have been much earlier.
And putting --signoff after --log is still alphabetical in v2.15.0-rc1
(ignoring a few outliers). So I don't think it's a reason to change
where I'd put the option, but in v3 of this patch I'll update the
commit message to cite 7c85d274 when motivating the location.
Cheers,
Trevor
--
This email may be signed or encrypted with GnuPG (http://www.gnupg.org).
For more information, see http://en.wikipedia.org/wiki/Pretty_Good_Privacy
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-10-12 9:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-11 20:10 [PATCH] pull: pass --signoff/--no-signoff to "git merge" W. Trevor King
2017-10-12 1:17 ` Junio C Hamano
2017-10-12 5:30 ` W. Trevor King
2017-10-12 5:42 ` Junio C Hamano
2017-10-12 6:23 ` W. Trevor King
2017-10-12 11:08 ` Junio C Hamano
2017-10-12 8:46 ` [PATCH v2] " W. Trevor King
2017-10-12 9:18 ` W. Trevor King [this message]
2017-10-12 10:11 ` Junio C Hamano
2017-10-12 18:35 ` [PATCH v3] " W. Trevor King
2017-10-13 1:48 ` 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
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=20171012091822.GA27403@valgrind.us \
--to=wking@tremily.us \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=lukaszgryglicki@o2.pl \
/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).