threads / discuss / 46501

git send-email -v n fails

Subject: git send-email -v n fails

## tl;dr

2 messages between Aug 2, 2017 and Aug 2, 2017.

replies: 1people: 2as markdown or json

Olaf Hering· Aug 2, 2017, 13:46 UTC · lore

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· Aug 2, 2017, 16:35 UTC · re: Olaf Hering · lore

Re: git send-email -v n fails

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.

← back to recent threads