[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20181019070001.GA30556@lst.de>
Date: Fri, 19 Oct 2018 09:00:01 +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 Wed, Oct 17, 2018 at 10:30:49AM +0200, Geert Uytterhoeven wrote:
> Please use "git format-patch -v<N> --cover" to prepare patch series
> for sending with git-send-email.
>
> "-v<N>" to prefix all patches with version number <N>,
> "--cover" to have a "[PATCH 0/<M>]" prefix in the cover letter.
We had that discussion before and I strongly disagree with messing
up the subject lines like that. The git-send-email defaults are
perfectly fine.
Powered by blists - more mailing lists