Hi Christoph,
On Fri, Oct 19, 2018 at 9:00 AM Christoph Hellwig <hch@xxxxxx> 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@xxxxxxxxxxxxxx
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
