From: Junio C Hamano <gitster@pobox.com>
To: "Chinmoy via GitGitGadget" <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org, Bagas Sanjaya <bagasdotme@gmail.com>,
Philip Oakley <philipoakley@iee.email>,
Chinmoy <chinmoy12c@gmail.com>
Subject: Re: [PATCH v4] column, range-diff: downcase option description
Date: Mon, 29 Mar 2021 14:05:32 -0700 [thread overview]
Message-ID: <xmqqmtulisbn.fsf@gitster.g> (raw)
In-Reply-To: <pull.920.v4.git.1617029194872.gitgitgadget@gmail.com> (Chinmoy via GitGitGadget's message of "Mon, 29 Mar 2021 14:46:34 +0000")
"Chinmoy via GitGitGadget" <gitgitgadget@gmail.com> writes:
> From: Chinmoy Chakraborty <chinmoy12c@gmail.com>
>
> It is customary not to begin the help text for each option given to
> the parse-options API with a capital letter. Various (sub)commands'
> option arrays don't follow the guideline provided by the parse_options
> Documentation regarding the descriptions.
>
> Downcase the first word of some option descriptions for "column"
> and "range-diff".
>
> Signed-off-by: Chinmoy Chakraborty <chinmoy12c@gmail.com>
> ---
Thanks, Chinmoy, Bagas and Philip. Will queue.
prev parent reply other threads:[~2021-03-29 21:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-28 6:34 [PATCH] Documentation: amended usages of various (sub)commands Chinmoy via GitGitGadget
2021-03-28 6:56 ` Bagas Sanjaya
2021-03-28 8:13 ` Bagas Sanjaya
2021-03-28 8:24 ` Chinmoy Chakraborty
2021-03-28 18:32 ` Junio C Hamano
2021-03-29 5:17 ` Bagas Sanjaya
2021-03-28 10:16 ` [PATCH v2] Documentation: make (sub)command options conform to TD of option parsing Chinmoy via GitGitGadget
2021-03-29 10:45 ` [PATCH v3] column, range-diff: downcase option description Chinmoy via GitGitGadget
2021-03-29 10:58 ` Bagas Sanjaya
2021-03-29 13:46 ` Philip Oakley
2021-03-29 14:46 ` [PATCH v4] " Chinmoy via GitGitGadget
2021-03-29 21:05 ` 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=xmqqmtulisbn.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=bagasdotme@gmail.com \
--cc=chinmoy12c@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=philipoakley@iee.email \
/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.