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

Re: [PATCH] git-send-email: parse all messages in mbox

From
Jay Soffian <jaysoffian@gmail.com>
Date
May 14, 2009, 14:48 UTC
Message-ID
<76718490905140748n390d0e85t8349b69fc6debc2a@mail.gmail.com>
In-Reply-To
<873abbeoqc.wl%vmayatsk@redhat.com>

On Mon, May 11, 2009 at 9:46 AM, Vitaly Mayatskikh <v.mayatskih@gmail.com> wrote:

> Currently git-send-email sends all mbox in one email. This seems to be wrong,
> because mbox can contain several messages. For example,
> `git format-patch --stdout' forms mbox file with all patches in it.
Just out of curiosity, what is the motivation for this patch?

By default, format-patch generates a file per commit, which is what send-email currently expects. You can also specify one or more commits to send-email directly, in which case it runs format-patch on your behalf. And, send-email cannot handle messages on stdin, so "git format-patch | git send-email" is not a valid workflow, even after this patch.

So the only way I can see this being useful is if you're doing something like:

$ git format-patch --stdout > mbox $ git send-email mbox

Or you can combine those in bash with:
$ git send-email <(git format-patch --stdout)

But, why? The only way this patch would make any sense to me is if it _also_ extended send-email to read its messages from stdin.

j.
Previous: Vitaly MayatskikhNext: Vitaly Mayatskikh
Message 4 of 5 in “git-send-email: parse all messages in mbox”
  1. git-send-email: parse all messages in mboxVitaly Mayatskikh, May 11, 2009
  2. Junio C HamanoMay 12, 2009
  3. Vitaly MayatskikhMay 14, 2009
  4. Jay SoffianMay 14, 2009
  5. Vitaly MayatskikhMay 14, 2009

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.