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

Re: [PATCH 0/2] Update git-send-email-script with --compose

From
Junio C Hamano <junkio@cox.net>
Date
Sep 5, 2005, 21:10 UTC
Message-ID
<7vek832pbk.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<46a038f905090513456d67842b@mail.gmail.com>
Martin Langhoff <martin.langhoff@gmail.com> writes:
> It shows that I was never familiar with the practices of linux
> hackers. I've always read the references to mboxes holding patchbombs
> meaning literally one mbox file with a zillion contatenated patches
> received via email.

To be fair to you, it is _not_ the practices of Linux hackers. For one thing, I am not among them. I think it is perfectly reasonable to expect it to produce a single mailbox, like you expected.

The primary reason why "format-patch --mbox" only does one file per patch is because I am too lazy to add a --single-mbox option which does the "right thing". This _could_ be "fixed", but on the other hand the current one file per patch behaviour is arguably more flexible than always creating a single mbox, and that is what I use as an excuse to justify my laziness ;-).

Previous: Martin Langhoff
Message 10 of 10 in “Update git-send-email-script with --compose”
  1. 0/2 Update git-send-email-script with --composeRyan Anderson, Sep 5, 2005
  2. 1/2 Make git-send-email-script ignore some unnecessary options when operating in batch mode.Ryan Anderson, Sep 5, 2005
  3. 2/2 Update documentation of --compose to git-send-email-script.txtRyan Anderson, Sep 5, 2005
  4. Martin LanghoffSep 5, 2005
  5. Ryan AndersonSep 5, 2005
  6. Junio C HamanoSep 5, 2005
  7. Martin LanghoffSep 5, 2005
  8. Junio C HamanoSep 5, 2005
  9. Martin LanghoffSep 5, 2005
  10. Junio C HamanoSep 5, 2005

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.