[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20181019120159.GA14677@lst.de>
Date: Fri, 19 Oct 2018 14:01:59 +0200
From: Christoph Hellwig <hch@....de>
To: Geert Uytterhoeven <geert@...ux-m68k.org>
Cc: Christoph Hellwig <hch@....de>,
Masahiro Yamada <yamada.masahiro@...ionext.com>,
Matt Porter <mporter@...nel.crashing.org>,
Alex Bounine <alex.bou9@...il.com>,
Dominik Brodowski <linux@...inikbrodowski.net>,
linux-kbuild <linux-kbuild@...r.kernel.org>,
linux-pci <linux-pci@...r.kernel.org>,
scsi <linux-scsi@...r.kernel.org>,
Linux-Arch <linux-arch@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
linuxppc-dev <linuxppc-dev@...ts.ozlabs.org>
Subject: Re: move bus (PCI, PCMCIA, EISA, rapdio) config to drivers/ v2
On Fri, Oct 19, 2018 at 09:22:08AM +0200, Geert Uytterhoeven wrote:
> Hi Christoph,
>
> On Fri, Oct 19, 2018 at 9:10 AM Christoph Hellwig <hch@....de> wrote:
> > On Fri, Oct 19, 2018 at 09:07:51AM +0200, Geert Uytterhoeven wrote:
> > > Without this:
> > > - It's hard to visually match your untagged cover letter with the
> > > actual patches,
> > > - Your individual patches lack the version info, so people cannot see which
> > > version review comments in an email reply apply to.
> >
> > All of that is trivially solved by mail threading.
>
> You forgot to answer this question:
>
> | Can you please clarify what exactly that would mess up?
It makes the already limited space in the subject line even shorted
(or harder to read depending on which way you go) for absolutely not
good reason.
Powered by blists - more mailing lists