On Fri, Oct 23, 2015 at 10:49:51AM +0200, Peter Zijlstra wrote: > On Fri, Oct 23, 2015 at 04:33:02AM +0200, Frederic Weisbecker wrote: > > I personally (and I think this is the general LKML behaviour) use in-reply-to > > when I post a single patch that is a fix for a bug, or a small enhancement, > > discussed on some thread. It works well as it fits the conversation inline. > > > > But for anything that requires significant changes, namely a patchset, > > and that includes a new version of such patchset, it's usually better > > to create a new thread. Otherwise the thread becomes an infinite mess and it > > eventually expands further the mail client columns. > > Agreed, although for single patches I use my regular mailer (mutt) and > can't be arsed with tools. Yeah me too, otherwise I can't write a text before the patch changelog. > Also I don't actually use git-send-email ever, so I might be biased. Ah it's just too convenient so I wrote my scripts on top of it :-) But surely many mail sender libraries can post patches just fine as well. -- To unsubscribe from this list: send the line "unsubscribe linux-api" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
