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

Re: [PATCH] send-email: Clear To: field for every mail

From
Junio C Hamano <gitster@pobox.com>
Date
Oct 4, 2010, 07:09 UTC
Message-ID
<7v7hhya0yc.fsf@alter.siamese.dyndns.org>
In-Reply-To
<a9b17bd454e57abb75f6cd2a7da63ec7738f5e7b.1286170305.git.viresh.kumar@st.com>
Viresh KUMAR <viresh.kumar@st.com> writes:
Show 7 quoted lines
> While sending multiple patches with a single git-send-email command,
> To: field is not cleared after every mail. This patch clears To: field
> after every patch sent.
>
> Signed-off-by: Viresh Kumar <viresh.kumar@st.com>
> Tested-by: Viresh Kumar <viresh.kumar@st.com>
> ---

Heh, are people who send patches with only S-o-b by your definition not testing their patches at all ;-)? As far as I can tell, your patch applied to 'next' will break t9001 rather badly.

I agree there is a bug that you are trying to address in the series by Stephen that keeps adding To: address that is read from an earlier output of format-patch created with its --to option, but I do not think this is a right fix. Have you tested sending a series with a plain format-patch output without extraneous To:, Cc: and such headers?

A normal send-email session takes the recipient address from either --to or interactively upfront, and then use those addresses kept in @to variable in the loop, repeatedly. I do not see anything in your patch to avoid losing these addresses.

Previous: Joe PerchesNext: viresh kumar
Message 8 of 9 in “send-email: Clear To: field for every mail”
  1. send-email: Clear To: field for every mailViresh KUMAR, Oct 4, 2010
  2. send-email: Don't leak To: headers between patchesStephen Boyd, Oct 4, 2010
  3. Junio C HamanoOct 4, 2010
  4. Ævar Arnfjörð BjarmasonOct 4, 2010
  5. Ævar Arnfjörð BjarmasonOct 4, 2010
  6. Junio C HamanoOct 4, 2010
  7. Joe PerchesOct 4, 2010
  8. Junio C HamanoOct 4, 2010
  9. viresh kumarOct 4, 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.