From: Erik Faye-Lund <kusmabite@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Richard Yang <weiyang@linux.vnet.ibm.com>, git@vger.kernel.org
Subject: Re: How can I specify the "sendmail" program for git-send-email?
Date: Mon, 11 Jun 2012 18:25:47 +0200 [thread overview]
Message-ID: <CABPQNSaLtdGVfdkQyRFn4_Ze84zGVuvPwxTpr3hY8uDc0WU2Zg@mail.gmail.com> (raw)
In-Reply-To: <7v4nqh96z5.fsf@alter.siamese.dyndns.org>
On Mon, Jun 11, 2012 at 5:57 PM, Junio C Hamano <gitster@pobox.com> wrote:
> Erik Faye-Lund <kusmabite@gmail.com> writes:
>
>> Well, I've always been slightly annoyed by the "send-mail" vs
>> "sendemail" inconsistency.
>
> Hrm, isn't it between "sendmail" (as in /usr/lib/sendmail) and
> "send-email" (a subcommand of git)?
>
Ugh, you are right. My brain must have been defective :)
>> Perhaps we could do something along these
>> lines (plus all documentation-updates, omitted for clarity) to reduce
>> the risk of confusion?
>
> Assuming that the contrast between "sendmail" and "git send-email"
> is what you are trying to address, I fail to see how it would help
> reducing the confusion if you start naming configuration variables
> used by "git send-email" without E.
>
No, this was just me being a moron.
> If the proposal were to give "send-email.$var" synomyms to
> corresponding "sendemail.$var" variables, I would have been
> persuaded to believe it may alleviate potential confusion, though.
This was really the way I wanted to go, but I somehow got unsure about
the legality of the dashes in config sections. I'm a bit skeptical to
introducing new non-letter characters if we don't have to.
So let's just drop my suggestion. I wasn't thinking straight.
prev parent reply other threads:[~2012-06-11 16:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-11 7:32 How can I specify the "sendmail" program for git-send-email? Richard Yang
2012-06-11 8:23 ` Erik Faye-Lund
2012-06-11 9:04 ` Richard Yang
2012-06-11 9:15 ` Erik Faye-Lund
2012-06-11 9:25 ` konglu
2012-06-11 9:45 ` Erik Faye-Lund
2012-06-11 10:13 ` konglu
2012-06-11 15:57 ` Junio C Hamano
2012-06-11 16:25 ` Erik Faye-Lund [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CABPQNSaLtdGVfdkQyRFn4_Ze84zGVuvPwxTpr3hY8uDc0WU2Zg@mail.gmail.com \
--to=kusmabite@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=weiyang@linux.vnet.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).