From: Junio C Hamano <gitster@pobox.com>
To: "Quentin Nerden via GitGitGadget" <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org, Quentin Nerden <quentin.nerden@intel.com>
Subject: Re: [PATCH v2 2/2] docs: git-clone: list short form of options first
Date: Tue, 02 Jul 2019 12:14:16 -0700 [thread overview]
Message-ID: <xmqqwoh02qrb.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <c562cf681f5c1c47cd77eead30ec9ae1eb7ca9e0.1562078259.git.gitgitgadget@gmail.com> (Quentin Nerden via GitGitGadget's message of "Tue, 02 Jul 2019 07:37:41 -0700 (PDT)")
"Quentin Nerden via GitGitGadget" <gitgitgadget@gmail.com> writes:
> From: Quentin Nerden <quentin.nerden@intel.com>
>
> List the short form of options (e.g.: '-l') before the long form (e.g.
> '--local').
> This is to match the doc of git-add, git-commit, git-clean, git-branch...
>
> Signed-off-by: Quentin Nerden <quentin.nerden@gmail.com>
> ---
> Documentation/git-clone.txt | 18 +++++++++---------
> 1 file changed, 9 insertions(+), 9 deletions(-)
Much easier to follow ;-) Thanks.
prev parent reply other threads:[~2019-07-02 19:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-27 19:16 [PATCH 0/1] Update git-clone doc: refer to long option Quentin Nerden via GitGitGadget
2019-06-27 19:17 ` [PATCH 1/1] docs: update git-clone doc: refer to long options Quentin Nerden via GitGitGadget
2019-06-27 20:10 ` Junio C Hamano
2019-06-28 11:55 ` Johannes Schindelin
2019-07-02 14:37 ` [PATCH v2 0/2] Update git-clone doc: refer to long form of the options and list short form of the options first Quentin Nerden via GitGitGadget
2019-07-02 14:37 ` [PATCH v2 1/2] docs: git-clone: refer to long form of options Quentin Nerden via GitGitGadget
2019-07-02 14:37 ` [PATCH v2 2/2] docs: git-clone: list short form of options first Quentin Nerden via GitGitGadget
2019-07-02 19:14 ` 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
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=xmqqwoh02qrb.fsf@gitster-ct.c.googlers.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=quentin.nerden@intel.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.
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).