Re: [PATCH v5 3/3] send-email docs: add format-patch options

Carlo Arenas [off-list ref] writes:

quoted

Or do you mean

        git send-email <options>

and have the <options> placeholder to stand for both send-email
options and options meant for format-patch?

the later AND including a non optional part that explains that you
need to indicate some sort of revision ...

Ah, thanks for explanation.

    git format-patch -2

would be options-only way to "indicate some sort of revision", so
perhaps 

    . git send-email <send-email options> files|directory
    . git send-email <send-email options> <format-patch options>

(where "options" is used to refer to both --options and arguments)
would illustrate the differences better?

On 25/09/21 03.03, Junio C Hamano wrote:

Ah, thanks for explanation.

     git format-patch -2

would be options-only way to "indicate some sort of revision", so
perhaps

     . git send-email <send-email options> files|directory
     . git send-email <send-email options> <format-patch options>

(where "options" is used to refer to both --options and arguments)
would illustrate the differences better?

But we can also directly specify revision range (commonly <common 
ancestor>..HEAD or HEAD ^<common ancestor>).

So for the second form, the syntax will be:

   git send-email <send-email options> <format-patch options> <revision 
range>

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