git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [RFC PATCH] git-send-email.txt: clarify which options take an argument.

From
Matthieu Moy <matthieu.moy@imag.fr>
Date
Apr 7, 2009, 16:59 UTC
Message-ID
<vpqvdpg8knl.fsf@bauges.imag.fr>
In-Reply-To
<2faad3050904070806o55ba937cy1e5cd4fd156a4352@mail.gmail.com>
Baz <brian.ewins@gmail.com> writes:
Show 27 quoted lines
> 2009/4/7 Matthieu Moy <Matthieu.Moy@imag.fr>:
>> ---
>>
>> Can someone more knowledgeable than me proof-read this? I tried to use
>> intuitive names for the arguments (like 'address' where an email
>> address is expected), but since there are options I never used, I may
>> have mis-understood some of them.
>>
>> Thanks,
>>
>>  Documentation/git-send-email.txt |   36 ++++++++++++++++++------------------
>>  1 files changed, 18 insertions(+), 18 deletions(-)
>>
>> diff --git a/Documentation/git-send-email.txt b/Documentation/git-send-email.txt
>> index 10dfd66..e25da71 100644
>> --- a/Documentation/git-send-email.txt
>> +++ b/Documentation/git-send-email.txt
>> @@ -39,13 +39,13 @@ OPTIONS
>>  Composing
>>  ~~~~~~~~~
>>
>> ---bcc::
>> +--bcc='address'::
>>        Specify a "Bcc:" value for each email. Default is the value of
>>        'sendemail.bcc'.
>
> A general comment: the other man pages use a style like "--bcc=<address>".

Almost all ;-). A quick grep showed me git-rev-list.txt and I did the same. I'll send another patch to make it consistant.

Show 8 quoted lines
>> +--smtp-encryption='mode'::
>>        Specify the encryption to use, either 'ssl' or 'tls'.  Any other
>>        value reverts to plain SMTP.  Default is the value of
>>        'sendemail.smtpencryption'.
>
> Maybe <encryption-mode> here. You use <mode> for other options below
> to mean something else. However, I doubt the use is all that
> confusing.

Changed to just "encryption", since this is the word used just below in the sentence.

Show 9 quoted lines
>> ---cc-cmd::
>> +--cc-cmd='cmd'::
>>        Specify a command to execute once per patch file which
>>        should generate patch file specific "Cc:" entries.
>>        Output of this command must be single email address per line.
>>        Default is the value of 'sendemail.cccmd' configuration value.
>
> Why not <command>? The option is short to save typing, doesn't mean
> its documentation has to be.
Done.
Show 7 quoted lines
>> ---[no-]validate::
>> +--[no-]validate='mode'::
>>        Perform sanity checks on patches.
>>        Currently, validation means the following:
>
> Is this one correct? Don't you just type --validate, or --no-validate,
> without a value?
Fixed too.
Thanks, new patch follows.
-- 
Matthieu
Previous: BazNext: Matthieu Moy
Message 4 of 6 in “git-send-email.txt: clarify which options take an argument.”
  1. git-send-email.txt: clarify which options take an argument.Matthieu Moy, Apr 7, 2009
  2. BazApr 7, 2009
  3. BazApr 7, 2009
  4. Matthieu MoyApr 7, 2009
  5. 1/2 git-send-email.txt: clarify which options take an argument.Matthieu Moy, Apr 7, 2009
  6. 2/2 git-rev-list.txt: make ascii markup uniform with other pages.Matthieu Moy, Apr 7, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.