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

Re: git-format-patch little gripe

From
LTLuben Tuikov <ltuikov@yahoo.com>
Date
Nov 3, 2006, 20:37 UTC
Message-ID
<20061103203752.26472.qmail@web31810.mail.mud.yahoo.com>
In-Reply-To
<20061103185026.GA28566@coredump.intra.peff.net>
--- Jeff King <peff@peff.net> wrote:
Show 23 quoted lines
> For my own workflow, I don't want to have to pick the commit out of
> rev-list (or log) output. I want to find it and hit a button to say "OK,
> now mail this patch." So I put _all_ of my patches into an mbox, and
> then browse them with mutt. Sort of a poor man's patch browser, but then
> I'm ready to jump into mailing them immediately.
> 
> I use the following script:
> 
> #!/bin/sh
> root=${1:-origin}
> git-format-patch -s --stdout $root >.mbox
> mutt -f .mbox
> rm -f .mbox
> 
> And then in mutt, I use this macro to bind 'b' to editing the full
> message w/ headers:
> 
> macro index b ":set edit_headers=yes<enter><resend-message>:set edit_headers=no<enter>"
> 
> I know that may be useless if you're not using mutt, but I just wanted
> to stimulate some discussion among patch submitters about how they
> actually do it. I'm not sure how configurable tig is, but it shouldn't
> be too hard to add something like this to it.
That's very cool!
   Luben
Previous: Jeff KingNext: Sean
Message 3 of 6 in “git-format-patch little gripe”
  1. Luben TuikovNov 3, 2006
  2. Jeff KingNov 3, 2006
  3. Luben TuikovNov 3, 2006
  4. SeanNov 25, 2006
  5. Jeff KingNov 25, 2006
  6. SeanNov 25, 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.