[RFC] Patchsets in a single mail? [Re: [PATCH 01/55] Add simple subunit runner outputting subunit v1.]

[Simo]

On Sat, 2015-02-14 at 15:50 +0100, Volker Lendecke wrote:
> On Sat, Feb 14, 2015 at 04:18:21AM -0800, Christoph Hellwig wrote:
> > On Sat, Feb 14, 2015 at 10:56:21AM +0100, Volker Lendecke wrote:
> > > On Fri, Feb 13, 2015 at 06:00:47PM -0500, Simo wrote:
> > > > Because they have mail clients that make it easy to deal with them :-)
> > > 
> > > Do you have special tricks for mutt? Or do we have to switch
> > > MUAs?
> > 
> > What's your problem with mutt and threaded patch sets?  I deal with them
> > on various mailing lists all day long and I can't even think of a
> > problem.
> 
> It's just that I prefer to see a patchset as a whole instead
> of many different mails that I have to apply individually,
> one by one. All possible, just inconvenient for me. Not all
> patches are perfect on their own, they only make sense in a
> larger series. Having them in individual mails loses
> coherence, least for me.
> 
> My question about mutt was triggered by Simo indicating
> that there are MUAs that make handling those patch groups
> easier. And as I use mutt normally, I asked him for mutt
> tricks.
> 
> If dealing with patchsets as individual mails means I have
> to switch to a graphical mail client like Thunderbird I will
> not do it just for that and just delete those multi-dozen
> patch mail floods that fill my inbox.

Well I do not use mutt indeed, when a patchset comes in different emails
I deal with it in various ways.

One way is to save the whole thread (normally these patchset have a
header (00/00) email to which all others refer to) and then git am the
mbox file. I believe you can easily do the same in mutt.

TBH, I strongly encourage people sending patchsets to actually provide a
link to a branch in a git tree with the same patchset, that way it is
easy to just git remote add/pull the branch and play with it in git+vim
which is my favorite way to look at patches.

Simo.