linux-kernel - Re: [PATCHSET v2 driver-core-next] kernfs, sysfs, driver-core: implement synchronous self-removal

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]

Date:	Sat, 11 Jan 2014 12:19:09 -0800
From:	Greg KH <gregkh@...uxfoundation.org>
To:	Tejun Heo <tj@...nel.org>
Cc:	Alan Stern <stern@...land.harvard.edu>,
	linux-kernel@...r.kernel.org, schwidefsky@...ibm.com,
	heiko.carstens@...ibm.com, JBottomley@...allels.com,
	bhelgaas@...gle.com
Subject: Re: [PATCHSET v2 driver-core-next] kernfs, sysfs, driver-core:
 implement synchronous self-removal

On Sat, Jan 11, 2014 at 01:51:10PM -0500, Tejun Heo wrote:
> Hey, Alan.
> 
> On Fri, Jan 10, 2014 at 10:46:10AM -0500, Alan Stern wrote:
> > The SUBJECT lines in your patch emails don't mention the version
> > number.  That is, they just say "[PATCH]", not "[PATCH v2]" or "[PATCH
> > v3]". This makes it very difficult for me to tell which messages to
> > read.
> 
> Hmm... they're all threaded.  I add version tags when posting
> incremental patches but usually don't bother with it when posting a
> new version of the whole series.  After all, some patches are get
> updated without explicitly given a new version for refrehses and stuff
> so it's not like you can determine everything based on subjects only.
> 
> > (Reading them in order doesn't work, because my computer mixes up the 
> > order of messages when it downloads a large bunch from the email 
> > server.  It's kind of annoying...)
> 
> And they aren't threaded?

They were all threaded for me, perhaps Alan needs a better email client :)
--
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/