public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
	linux-kernel@vger.kernel.org,
	linux-usb-devel@lists.sourceforge.net
Subject: Re: [linux-usb-devel] [GIT PATCH] USB fixes for 2.6.23-rc3
Date: Thu, 23 Aug 2007 16:28:31 -0700	[thread overview]
Message-ID: <20070823232831.GA4638@suse.de> (raw)
In-Reply-To: <20070823161815.604f1a8b.rdunlap@xenotime.net>

On Thu, Aug 23, 2007 at 04:18:15PM -0700, Randy Dunlap wrote:
> 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)

I use git-send-email these days, and it already supports this with the
--no-chain-reply-to option.  I'll consider using it next time, if at
least one more person complains about this :)

> 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.

Yeah, you are right that things are now numbered, so it might be better
(my old send_lots_of_email.pl script didn't number things very well, if
at all from what I remember).  But odds are, I'll
still get complaints.  But hey, it looks like people will complain
either way :)

thanks,

greg k-h

  reply	other threads:[~2007-08-23 23:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-22 22:08 [GIT PATCH] USB fixes for 2.6.23-rc3 Greg KH
2007-08-23 22:43 ` [linux-usb-devel] " Guennadi Liakhovetski
2007-08-23 22:49   ` Greg KH
2007-08-23 23:01     ` Guennadi Liakhovetski
2007-08-23 23:18     ` Randy Dunlap
2007-08-23 23:28       ` Greg KH [this message]
2007-08-23 23:31         ` Adrian Bunk
2007-08-24  0:02           ` Greg KH

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20070823232831.GA4638@suse.de \
    --to=gregkh@suse.de \
    --cc=g.liakhovetski@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --cc=rdunlap@xenotime.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox