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

Re: Features ask for git-send-email

From
David Woodhouse <dwmw2@infradead.org>
Date
May 2, 2006, 14:14 UTC
Message-ID
<1146579255.17934.8.camel@pmac.infradead.org>
In-Reply-To
<e37km0$vav$1@sea.gmane.org>
On Tue, 2006-05-02 at 14:53 +0200, Jakub Narebski wrote:
> Doesn't 
>         Content-Type: text/plain; charset=$charset
> header need also
>         MIME-Version: 1.0

Maybe. The use of Content-Type: actually predates RFC2045, and if we include a MIME-Version header then we should make 100% sure that we also conform to the rest of RFC2045, which I hadn't actually looked at. In particular, we should take care of Content-Transfer-Encoding.

I'd prefer to leave MIME-Version out for now, I think.
-- 
dwmw2
Previous: Jakub NarebskiNext: Jakub Narebski
Message 4 of 8 in “Features ask for git-send-email”
  1. Bertrand JacquinApr 29, 2006
  2. David WoodhouseMay 2, 2006
  3. Jakub NarebskiMay 2, 2006
  4. David WoodhouseMay 2, 2006
  5. Jakub NarebskiMay 2, 2006
  6. Bertrand JacquinMay 2, 2006
  7. David WoodhouseMay 2, 2006
  8. Bertrand JacquinMay 2, 2006

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.