All of lore.kernel.org
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Christoph Hellwig <hch@lst.de>
Cc: Masahiro Yamada <yamada.masahiro@socionext.com>,
	Matt Porter <mporter@kernel.crashing.org>,
	Alex Bounine <alex.bou9@gmail.com>,
	Dominik Brodowski <linux@dominikbrodowski.net>,
	linux-kbuild <linux-kbuild@vger.kernel.org>,
	linux-pci <linux-pci@vger.kernel.org>,
	scsi <linux-scsi@vger.kernel.org>,
	Linux-Arch <linux-arch@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linuxppc-dev <linuxppc-dev@lists.ozlabs.org>
Subject: Re: move bus (PCI, PCMCIA, EISA, rapdio) config to drivers/ v2
Date: Fri, 19 Oct 2018 09:07:51 +0200	[thread overview]
Message-ID: <CAMuHMdXLug_T4onn23JormmYZXDWVnEFYaoMzA90bpGFvk6Eow@mail.gmail.com> (raw)
In-Reply-To: <20181019070001.GA30556@lst.de>

Hi Christoph,

On Fri, Oct 19, 2018 at 9:00 AM Christoph Hellwig <hch@lst.de> wrote:
> 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.

Can you please clarify what exactly that would mess up?
Documentation/process/submitting-patches.rst even mentions the tags
to put in "[PATCH <tag>]"?

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

WARNING: multiple messages have this Message-ID (diff)
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Christoph Hellwig <hch@lst.de>
Cc: Linux-Arch <linux-arch@vger.kernel.org>,
	scsi <linux-scsi@vger.kernel.org>,
	linux-kbuild <linux-kbuild@vger.kernel.org>,
	linux-pci <linux-pci@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Dominik Brodowski <linux@dominikbrodowski.net>,
	Masahiro Yamada <yamada.masahiro@socionext.com>,
	Alex Bounine <alex.bou9@gmail.com>,
	linuxppc-dev <linuxppc-dev@lists.ozlabs.org>
Subject: Re: move bus (PCI, PCMCIA, EISA, rapdio) config to drivers/ v2
Date: Fri, 19 Oct 2018 09:07:51 +0200	[thread overview]
Message-ID: <CAMuHMdXLug_T4onn23JormmYZXDWVnEFYaoMzA90bpGFvk6Eow@mail.gmail.com> (raw)
In-Reply-To: <20181019070001.GA30556@lst.de>

Hi Christoph,

On Fri, Oct 19, 2018 at 9:00 AM Christoph Hellwig <hch@lst.de> wrote:
> 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.

Can you please clarify what exactly that would mess up?
Documentation/process/submitting-patches.rst even mentions the tags
to put in "[PATCH <tag>]"?

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

  reply	other threads:[~2018-10-19  7:08 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-17  8:01 move bus (PCI, PCMCIA, EISA, rapdio) config to drivers/ v2 Christoph Hellwig
2018-10-17  8:01 ` Christoph Hellwig
2018-10-17  8:01 ` [PATCH 1/8] aha152x: rename the PCMCIA define Christoph Hellwig
2018-10-17  8:01   ` Christoph Hellwig
2018-10-17  8:01 ` [PATCH 2/8] powerpc: remove CONFIG_PCI_QSPAN Christoph Hellwig
2018-10-17  8:01   ` Christoph Hellwig
2018-10-17  9:10   ` Benjamin Herrenschmidt
2018-10-17  8:01 ` [PATCH 3/8] powerpc: PCI_MSI needs PCI Christoph Hellwig
2018-10-17  8:01   ` Christoph Hellwig
2018-10-17  8:01 ` [PATCH 4/8] PCI: consolidate PCI config entry in drivers/pci Christoph Hellwig
2018-10-17  8:01   ` Christoph Hellwig
2018-10-19  5:07   ` Masahiro Yamada
2018-10-19  5:07     ` Masahiro Yamada
2018-10-19  7:02     ` Christoph Hellwig
2018-10-19  7:02       ` Christoph Hellwig
2018-10-19  5:19   ` Max Filippov
2018-10-19  5:19     ` Max Filippov
2018-10-17  8:01 ` [PATCH 5/8] pcmcia: allow PCMCIA support independent of the architecture Christoph Hellwig
2018-10-17  8:01   ` Christoph Hellwig
2018-10-17  8:01 ` [PATCH 6/8] rapidio: consolidate RAPIDIO config entry in drivers/rapidio Christoph Hellwig
2018-10-17  8:01   ` Christoph Hellwig
2018-10-19  4:53   ` Masahiro Yamada
2018-10-19  4:53     ` Masahiro Yamada
2018-10-17  8:02 ` [PATCH 7/8] eisa: consolidate EISA Kconfig entry in drivers/eisa Christoph Hellwig
2018-10-17  8:02   ` Christoph Hellwig
2018-10-19  4:46   ` Masahiro Yamada
2018-10-19  4:46     ` Masahiro Yamada
2018-10-19  7:06     ` Christoph Hellwig
2018-10-19  7:06       ` Christoph Hellwig
2018-10-19  4:48   ` Masahiro Yamada
2018-10-19  4:48     ` Masahiro Yamada
2018-10-17  8:02 ` [PATCH 8/8] kconfig: remove CONFIG_MCA leftovers Christoph Hellwig
2018-10-17  8:02   ` Christoph Hellwig
2018-10-17  8:30 ` move bus (PCI, PCMCIA, EISA, rapdio) config to drivers/ v2 Geert Uytterhoeven
2018-10-17  8:30   ` Geert Uytterhoeven
2018-10-19  7:00   ` Christoph Hellwig
2018-10-19  7:00     ` Christoph Hellwig
2018-10-19  7:07     ` Geert Uytterhoeven [this message]
2018-10-19  7:07       ` Geert Uytterhoeven
2018-10-19  7:10       ` Christoph Hellwig
2018-10-19  7:10         ` Christoph Hellwig
2018-10-19  7:22         ` Geert Uytterhoeven
2018-10-19  7:22           ` Geert Uytterhoeven
2018-10-19 12:01           ` Christoph Hellwig
2018-10-19 12:01             ` Christoph Hellwig

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAMuHMdXLug_T4onn23JormmYZXDWVnEFYaoMzA90bpGFvk6Eow@mail.gmail.com \
    --to=geert@linux-m68k.org \
    --cc=alex.bou9@gmail.com \
    --cc=hch@lst.de \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=linux@dominikbrodowski.net \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mporter@kernel.crashing.org \
    --cc=yamada.masahiro@socionext.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.