Re: [PATCH] git-send-email.txt: Add EXAMPLES section. Write 1st level sections in uppercase

Michael J Gruber [off-list ref] writes:

I don't use any options besides --dry-run and --cc, which is the point
of the config options ;) In config I have to, smtpserver (pointing to an
msmtp-script), bcc, suppresscc, aliasesfile, aliastype, but that depends
on the project, of course (git.git here).

I just think that using all these options on the command line is very
atypical.

Having to give too many options from the command line all the time is a
sure sign that the defaults for unconfigured case are bad (which may well
be true but is is hard to change without a good plan) and that it is not
clearly explained how to configure the defaults for the repository.

I do not think it is productive to give an overwhelming list that you
would rarely use (i.e. until you figure out a good set of defaults for the
project).

"Without any options, send-email will send patches (using
/usr/sbin/sendmail or /usr/lib/sendmail or localhost) using any from, cc
and subject lines contained in the patch files; you have to specify at
least --to, or else you will be prompted for it.

All defaults pertaining to composing and sending of the patch mails and
to automating this process can be changed with config options, see the
corresponding sections below."

Yes, I think we should proceed in this direction.

I liked your format-patch example with merge-base, I just liked it
better in format-patch's man page ;)

Likewise.