Phillip Wood <phillip.wood123@xxxxxxxxx> writes: >> +--empty-commit=(die|skip|asis):: >> + The command usually errors out when seeing an input e-mail >> + message that lacks a patch. When this option is set to >> + 'skip', skip such an e-mail message without outputting error. >> + When this option is set to 'asis', create an empty commit, >> + recording the contents of the e-mail message as its log. >> + 'die' is specified by default. > > This feels sufficiently similar to the case of handling empty commits > in 'git rebase' that it is worth trying to have a similar user > interface. Otherwise the two commands have two different option names > doing more or less the same thing. 'git rebase' has > --empty=[drop,keep,ask] where drop is the default. If am were to > accept --empty=[drop,keep,die] it would offer a similar user > experience. Ah, thanks for noticing. I like the three words you suggest. If we already have a similar option, we definitely should follow suit, and I think "--empty" would be a better fit than "--empty-commit" in the context of talking about the _input_ to "am".
