git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: git send-email doesn't take To: addresses from the patch

From
VKviresh kumar <viresh.kumar@st.com>
Date
Sep 1, 2010, 08:56 UTC
Message-ID
<4C7E1537.9030405@st.com>
In-Reply-To
<4C7E05B5.1050805@gmail.com>
On 9/1/2010 1:20 PM, Stephen Boyd wrote:
Show 18 quoted lines
> 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>
Previous: Stephen BoydNext: Stephen Boyd
Message 3 of 6 in “git send-email doesn't take To: addresses from the patch”
  1. viresh kumarAug 30, 2010
  2. Stephen BoydSep 1, 2010
  3. viresh kumarSep 1, 2010
  4. Stephen BoydSep 2, 2010
  5. viresh kumarSep 3, 2010
  6. Junio C HamanoSep 3, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.