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

Re: [PATCH] send-email: Honor multi-part email messages

From
Junio C Hamano <gitster@pobox.com>
Date
Jan 24, 2013, 19:11 UTC
Message-ID
<7vr4labdl0.fsf@alter.siamese.dyndns.org>
In-Reply-To
<CAEFUfsE-Ca=4jAyoaCtoeVYX0Etsn2Cj42OJm+nu4042JPJaBg@mail.gmail.com>
Shumkin Alexey <alex.crezoff@gmail.com> writes:
> I've meant you did not reply to my last message in this thread
> http://thread.gmane.org/gmane.comp.version-control.git/181791

Please repost the patch (with possible updates) for review when attempting to resurrect an ancient topic, instead of forcing people to hunt for an ancient message.

I think your patch is wrong. What happens when we see a Subject: line with a non-ascii on it that causes an early return of the loop before your new code has a chance to see Content-Type: header?

Previous: Shumkin Alexey
Message 7 of 7 in “send-email: Honor multi-part email messages”
  1. send-email: Honor multi-part email messagesAlexey Shumkin, Sep 20, 2011
  2. Junio C HamanoSep 20, 2011
  3. Alexey ShumkinSep 20, 2011
  4. Alexey ShumkinJan 24, 2013
  5. Junio C HamanoJan 24, 2013
  6. Shumkin AlexeyJan 24, 2013
  7. Junio C HamanoJan 24, 2013

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.