Skip to contentSkip to conversation

git send-email -v n fails

DISCUSSION Olaf Hering 2 participants 2 messages Aug 2, 2017

lore
Share & tools
lore
#0 lore raw

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

#1 lore raw
Quoted 1 line · Olaf Hering

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 ;-).

Quoted 2 lines

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.