git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sheng Yang <yasker@gmail.com>
To: git@vger.kernel.org
Subject: Ambiguous -from of git-send-email
Date: Sun, 31 Aug 2008 13:57:10 +0800	[thread overview]
Message-ID: <20080831055710.GA644@yukikaze> (raw)

Hi, all

A trivial problem here, but I think it can be handled more clearly.

Recently when I begin to use git-send-email with my private email
account, I found it didn't work as I expected. The problem is "From" of
the patch. I have to specify my company email in the "From" which meant
the author, but when I go with default value of git-send-email, I found
it omit the additional "From" of patch in the mailbody.

For example, I specified "my@company.com" in patch's "From: " when used
git-format-patch to generate it. And I use "my@home.com" to send the
mail.  But if I go with default setting of git-send-email, it said the
mail would be sent as "from my@company.com"(of course it can't). At
last, the sent mail only got "From my@home.com" in mail header, and
"From my@company.com" was omitted.

I've checked the git-send-email code, and found what's the real meaning
of "-from" specify in git-send-email is the email account(sender) rather
than the author. And if the sender is the same as the author, the first
line of patch "From: xxx" was omitted. But at least on my machine, the
from specified in the mail would be overwritten by MTA/ISP(well, I am
not sure which of them did this), so what's the content of "-from" is
not important, but if "-from" is the same as "From" in the patch, the
"From" line in the patch is omitted, otherwise the line is kept.

Yeah, it's reasonable. But I think it's not that clear. "-from" of
git-send-email indicated the sender and "From" indicated the author is
very ambiguous.  Maybe use "-sender" here in parameter is more
reasonable? And do we need some notes in manual?

And can we add a something like "sendemail.sender" to specify the
sender? I think it's not that unusual to make author's email address is
different from sender, at least I think it's more common than
"sendmail.bcc".

If you agree, I'd like to offer a patch for "sendemail.sender"(maybe
also give some note in manual for "-from").

Thanks!

--
regards
Yang, Sheng

             reply	other threads:[~2008-08-31  6:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-31  5:57 Sheng Yang [this message]
2008-08-31 19:37 ` Ambiguous -from of git-send-email Ask Bjørn Hansen
2008-08-31 20:32   ` [PATCH] Document sendemail.envelopesender configuration Ask Bjørn Hansen
2008-08-31 21:01     ` Jakub Narebski
2008-09-02  2:51       ` Ask Bjørn Hansen

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=20080831055710.GA644@yukikaze \
    --to=yasker@gmail.com \
    --cc=git@vger.kernel.org \
    /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).