Thread (1 message) 1 message, 1 author, 2016-06-15

Re: [PATCH] send-email: make annotate configurable

From: Junio C Hamano <hidden>
Date: 2016-06-15 22:53:32

Matthieu Moy [off-list ref] writes:
Junio C Hamano [off-list ref] writes:
...
quoted
As long as there is --no-annotate to cancel a configured value for
one-shot invocation (I didn't check, but it should be added if there isn't
already one), I think this change makes sense (I admit that I do not use
the --annotate option myself, though).
I almost always use --annotate, so this option definitely makes sense
for me (I usually call send-email through an alias that adds --annotate
anyway).
I do not doubt the usefulness of it, but if there is no --no-annotate, it
would make the new variable unusable for those who would never run it
without --annotate option; while you said "almost always", you didn't give
us any useful information, so I had to check ;-)  It turns out that

    $ git send-email --no-annotate </dev/null

errors out with "unrecognized argument: --no-annotate", which first needs
to be addressed before the configuration variable can become useful.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help