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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20070823232831.GA4638@suse.de>
Date:	Thu, 23 Aug 2007 16:28:31 -0700
From:	Greg KH <gregkh@...e.de>
To:	Randy Dunlap <rdunlap@...otime.net>
Cc:	Guennadi Liakhovetski <g.liakhovetski@....de>,
	linux-kernel@...r.kernel.org, linux-usb-devel@...ts.sourceforge.net
Subject: Re: [linux-usb-devel] [GIT PATCH] USB fixes for 2.6.23-rc3

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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/