[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.44L0.1401111751040.16586-100000@netrider.rowland.org>
Date: Sat, 11 Jan 2014 17:52:30 -0500 (EST)
From: Alan Stern <stern@...land.harvard.edu>
To: Greg KH <gregkh@...uxfoundation.org>
cc: Tejun Heo <tj@...nel.org>, <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, 11 Jan 2014, Greg KH wrote:
> 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.
Greg, what do you prefer in this situation?
> > > (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 :)
Undoubtedly I do. My current client is embarassingly old.
Alan Stern
--
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/
Powered by blists - more mailing lists