# git send-email -v n fails

2 messages from 2017-08-02 to 2017-08-02. Participants: Olaf Hering, Junio C Hamano.
Thread: https://gitlist.dev/t/46501

## Olaf Hering, 2017-08-02 13:46

Subject: git send-email -v n fails
Message-ID: <20170802134635.GA19311@aepfle.de>
URL: https://gitlist.dev/e/20170802134635.GA19311%40aepfle.de

```
I think send-email should understand all options of format-patch.
At least for '-v n' this fails, one has to type '--reroll-count n' as a
workaround with git version 2.13.3:

+ git send-email -v 2 --annotate --confirm=always --to-cmd=scripts/get_maintainer.pl 'HEAD^'
fatal: ambiguous argument '2': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'
format-patch -o /tmp/fVUtbB6OWI 1 HEAD^: command returned error: 128

Olaf

```

## Junio C Hamano, 2017-08-02 16:35

Subject: Re: git send-email -v n fails
Message-ID: <xmqqy3r2c4hl.fsf@gitster.mtv.corp.google.com>
URL: https://gitlist.dev/e/xmqqy3r2c4hl.fsf%40gitster.mtv.corp.google.com
In-Reply-To: <20170802134635.GA19311@aepfle.de>

```
Olaf Hering <olaf@aepfle.de> writes:

> I think send-email should understand all options of format-patch.

I actually think it was a mistake to allow send-email drive
format-patch ;-).

> At least for '-v n' this fails, one has to type '--reroll-count n' as a
> workaround with git version 2.13.3:

I wonder if "-v2" would work here, though.  It seems that the hack
send-email uses to "understand" format-patch options (i.e. the
subroutine is_format_patch_arg) is not prepared to take an option
with parameter.


```