From mboxrd@z Thu Jan 1 00:00:00 1970 From: Geert Uytterhoeven Subject: Re: move bus (PCI, PCMCIA, EISA, rapdio) config to drivers/ v2 Date: Fri, 19 Oct 2018 09:07:51 +0200 Message-ID: References: <20181017080201.10866-1-hch@lst.de> <20181019070001.GA30556@lst.de> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Return-path: In-Reply-To: <20181019070001.GA30556@lst.de> Sender: linux-kernel-owner@vger.kernel.org To: Christoph Hellwig Cc: Masahiro Yamada , Matt Porter , Alex Bounine , Dominik Brodowski , linux-kbuild , linux-pci , scsi , Linux-Arch , Linux Kernel Mailing List , linuxppc-dev List-Id: linux-arch.vger.kernel.org Hi Christoph, On Fri, Oct 19, 2018 at 9:00 AM Christoph Hellwig wrote: > On Wed, Oct 17, 2018 at 10:30:49AM +0200, Geert Uytterhoeven wrote: > > Please use "git format-patch -v --cover" to prepare patch series > > for sending with git-send-email. > > > > "-v" to prefix all patches with version number , > > "--cover" to have a "[PATCH 0/]" 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. Can you please clarify what exactly that would mess up? Documentation/process/submitting-patches.rst even mentions the tags to put in "[PATCH ]"? 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. Thanks! Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-vs1-f65.google.com ([209.85.217.65]:37483 "EHLO mail-vs1-f65.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726340AbeJSPMu (ORCPT ); Fri, 19 Oct 2018 11:12:50 -0400 MIME-Version: 1.0 References: <20181017080201.10866-1-hch@lst.de> <20181019070001.GA30556@lst.de> In-Reply-To: <20181019070001.GA30556@lst.de> From: Geert Uytterhoeven Date: Fri, 19 Oct 2018 09:07:51 +0200 Message-ID: Subject: Re: move bus (PCI, PCMCIA, EISA, rapdio) config to drivers/ v2 Content-Type: text/plain; charset="UTF-8" Sender: linux-arch-owner@vger.kernel.org List-ID: To: Christoph Hellwig Cc: Masahiro Yamada , Matt Porter , Alex Bounine , Dominik Brodowski , linux-kbuild , linux-pci , scsi , Linux-Arch , Linux Kernel Mailing List , linuxppc-dev Message-ID: <20181019070751.6T_5XC6B5-F156ehWVXK8_NmFK5J65P_aMeZfKhx_dM@z> Hi Christoph, On Fri, Oct 19, 2018 at 9:00 AM Christoph Hellwig wrote: > On Wed, Oct 17, 2018 at 10:30:49AM +0200, Geert Uytterhoeven wrote: > > Please use "git format-patch -v --cover" to prepare patch series > > for sending with git-send-email. > > > > "-v" to prefix all patches with version number , > > "--cover" to have a "[PATCH 0/]" 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. Can you please clarify what exactly that would mess up? Documentation/process/submitting-patches.rst even mentions the tags to put in "[PATCH ]"? 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. Thanks! Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds