[Ksummit-2012-discuss] [ATTEND] Your upstream maintainer just isn't that into you...

[James Bottomley]

On Thu, 2012-06-28 at 22:56 -0400, Steven Rostedt wrote:
> On Tue, 2012-06-26 at 16:52 -0700, Greg KH wrote:
> 
> > Hint, you can sort the emails and have mutt write them out properly.
> > 
> > Short example of how I do this:
> > 	tag the email thread to save:	Esc t
> > 	save them all to a new mbox:	; s ~/linux/work/s
> > 	quit mutt
> > 	open the new mbox:		mutt -f ~/linux/work/s
> > 	sort the messages:		o s
> > 	select them all:		ESC t
> > 	write them back out:		; s ~/linux/work/s
> > 	quit mutt
> > 	then apply the mbox:		git am -s ~/linux/work/s
> 
> This makes me not feel so bad for not using mutt much. I use Evilution
> just because it seems to work for me. I read LKML with mutt, but all my
> work and personal email is read with the bloat MUA.

Would you believe I do the same thing with evolution.  I actually have a
set of imap flags, one of which is 'patch to apply'.  I then have a
virtual search folder for each mailing list I apply patches from set to
the apply patch labels plus thread children (so I pick up the acks and
discussion).  The only twist with evolution is that it won't sort before
doing a multiple save, so I have a simple mboxorder shell script that
splits the mail by the number in the [PATCH 5/7] tag for applying.

> As for patch series, I never do the git am on a mbox of more than one
> patch. I review the patch, and then run the evolution filter command
> that sends the patch to my devel box, where I have a script to pull it
> in. I found review then pull, review then pull, works best for me. If I
> come across a patch I don't like, or where the entire series needs to be
> reverted, that's easy enough to revert it from git.

I do this in two windows: I do git am on the series, but after each
individual patch application I do various patch tests including a build
in the other window before moving on to the next patch.

James