Re: [RFC PATCH] Documentation: better document format-patch options in send-email

From: Bagas Sanjaya <bagasdotme@gmail.com>
Date: Oct 9, 2021, 11:04 UTC
Message-ID: <189cd45c-c550-8021-a1d1-b271bd4ecf57@gmail.com>
In-Reply-To: <CAPUEsphrNMPO_KaAmae02-DsxB9m1tBEK_Gnv29_mLQn0j2MkA@mail.gmail.com>

On 09/10/21 16.32, Carlo Arenas wrote:

Show 11 quoted lines

> The synopsis shows "send-email options" are also allowed (as
> optional), the mention of "relevant options" here was to indicate
> additional options from git-format-patch which make sense (ex: common
> diff options, --root, or the options from the range section of
> references).
> 
> The truth is that you can actually do files, directories and revisions
> now, but that is a bug.
> 
> Carlo
>

git send-email behaves similar to ln(1), depending on what options and arguments that are passed. See my attempted patch [1] for the wording.

[1]: https://lore.kernel.org/git/20210924121352.42138-1-bagasdotme@gmail.com/

For SYNOPSIS for file/directory and revision range, I suggest:

'git send-email' [<options>] <file|directory>... 'git send-email' [<send-email options>] [<format-patch options>] <revision range>

where <revision range> must be any forms that are accepted by git-format-patch(1).

-- 
An old man doll... just what I always wanted! - Clara