Re: [linux-usb-devel] [GIT PATCH] USB fixes for 2.6.23-rc3

[Randy Dunlap]

On Thu, 23 Aug 2007 15:49:56 -0700 Greg KH wrote:

> On Fri, Aug 24, 2007 at 12:43:47AM +0200, Guennadi Liakhovetski wrote:
> > Hi Greg,
> > 
> > sorry, this is a private egoistic request, so I took the liberty and 
> > removed Linus and Andrew from CC: If this wouldn't make things more 
> > difficult / worse for you and anyone else, could you perhaps post such 
> > patch chains as a reply to the first message (patch 0/x) and not each 
> > subsequent patch as a reply to the previous one? It would make it easier 
> > to view for _me_ (remember egoistic?) because my mail agent (pine) 
> > presents mail threads where every reply level produces a small right 
> > offset in the subject line, so, starting from about reply number 20 the 
> > subject is completely off-screen.
> > 
> > Again, this is a minor trouble, and, perhaps, I am the only one suffering 
> > from it, but if it doesn't matter either way for everyone else, I would 
> > really appreciate it that way.
> 
> Heh, people ask me about this every few months or so, so you are not
> alone.

I'd prefer that change also.  In fact I just modified (trivial)
send_lots_of_email.pl (gregkh_patchbomb mailer) to do this,
except that I just have it create an mbox that I email via
msmtp.  (and it reads a 'sendpatchset' control file for input
instead of needing to modify the script source file itself)


> Unfortunately, I really like the cascade affect, it shows that the
> patches do have to be applied in consecutive order for them to work
> properly (which some people seem to forget and then get mad at me when
> they try to cherry-pick intermediate patches and apply them to older
> kernels for odd reasons...)

A patch series such as:

PATCH 0/n: intro/summary
|_ PATCH 1/n: desc1
|_ PATCH 2/n: desc2
|_ PATCH 3/n: desc3

should imply a patch order also, shouldn't it?  At least it does
to me and to users of Paul Jackson's 'sendpatchset' script,
which acts in this way.

> If I wanted to respond in an egotistical way, I could just tell you to
> use an email client that can handle the cascade affect properly, like
> mine does :)


---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/