All of lore.kernel.org
 help / color / mirror / Atom feed
From: viresh kumar <viresh.kumar@st.com>
To: Stephen Boyd <bebarino@gmail.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: git send-email doesn't take To: addresses from the patch
Date: Wed, 1 Sep 2010 14:26:23 +0530	[thread overview]
Message-ID: <4C7E1537.9030405@st.com> (raw)
In-Reply-To: <4C7E05B5.1050805@gmail.com>

On 9/1/2010 1:20 PM, Stephen Boyd wrote:
> Subject: [PATCH] send-email: Use To: headers in patch files
> 
> It's a minor annoyance when you take the painstaking time to setup To:
> headers for each patch in a large series, and then go out to send the
> series with git-send-email and watch git ignore the To: headers in the
> patch files.
> 
> Therefore, always add To: headers from a patch file to the To: headers
> for that message. Keep the prompt for the blanket To: header so as to
> not break scripts (and user expectations). This means even if a patch has a
> To: header, git will prompt for the To: address. Otherwise, we'll need to
> introduce interface breakage to either request the header for each patch
> missing a To: header or default the header to whatever To: address is found
> first (be it in a patch or from user input). Both of these options don't seem
> very obvious/useful.
> 
> Reported-by: viresh kumar<viresh.kumar@st.com>
> Signed-off-by: Stephen Boyd<bebarino@gmail.com>

Tested-by: Viresh Kumar <viresh.kumar@st.com>

  reply	other threads:[~2010-09-01  8:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-30  7:05 git send-email doesn't take To: addresses from the patch viresh kumar
2010-09-01  7:50 ` Stephen Boyd
2010-09-01  8:56   ` viresh kumar [this message]
2010-09-02 18:36     ` Stephen Boyd
2010-09-03  4:02       ` viresh kumar
2010-09-03 17:18       ` Junio C Hamano

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=4C7E1537.9030405@st.com \
    --to=viresh.kumar@st.com \
    --cc=bebarino@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.