From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/9] Documentation cleanup
Date: Sat, 29 Mar 2014 11:28:38 +0100 [thread overview]
Message-ID: <20140329112838.0bee5010@skate> (raw)
In-Reply-To: <533697E6.5000804@trzebnica.net>
Dear Jerzy Grzegorek,
On Sat, 29 Mar 2014 10:52:38 +0100, Jerzy Grzegorek wrote:
> Regarding the "may be added", I agree.
> I proposed this change because I saw on mailing list both cases of
> submitting patch series introduced by a cover letter:
>
> * "in addition" case:
> [Patch vX 0/Y] ...
> [Patch vX 1/Y] ...
> ...
> [Patch vX Y/Y] ...
>
> * "instead" case:
> [Patch vX 0/Y] ...
> [Patch 1/Y] ...
> ...
> [Patch Y/Y] ...
To me, this second variant is wrong. This is because the cover letters
are not recorded by patchwork, so if the version is not mentioned in
the title of each individual patch, patchwork will not have the
information of the version of the patches.
> So maybe it should be:
> "Note that when your patch series is introduced by a cover letter,
> a patch version should be added to the cover letter in addition to
> the individual commits."
But is it really necessary? Such a wording seems to imply that the
contributor would have to do this manually, while the contributor
should instead simply use "git format-patch --subject-prefix", which
does just the right thing.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-03-29 10:28 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-28 21:24 [Buildroot] [PATCH 0/9] Documentation cleanup Jerzy Grzegorek
2014-03-28 21:24 ` [Buildroot] [PATCH 1/9] manual/configure.txt: reword part about internal toolchain backend Jerzy Grzegorek
2014-03-28 21:24 ` [Buildroot] [PATCH 2/9] manual/configure.txt: fix typo Jerzy Grzegorek
2014-03-28 21:32 ` Thomas Petazzoni
2014-03-28 23:01 ` Jerzy Grzegorek
2014-03-28 21:24 ` [Buildroot] [PATCH 3/9] manual/make-tips.txt: " Jerzy Grzegorek
2014-03-28 21:24 ` [Buildroot] [PATCH 4/9] manual/contribute.txt: " Jerzy Grzegorek
2014-03-28 21:24 ` [Buildroot] [PATCH 5/9] manual/contribute.txt: reword part about reporting issues Jerzy Grzegorek
2014-03-28 21:24 ` [Buildroot] [PATCH 6/9] manual/legal-notice.txt: fix typo Jerzy Grzegorek
2014-03-28 21:24 ` [Buildroot] [PATCH 7/9] manual/contribute.txt: reword part about versioning patches Jerzy Grzegorek
2014-03-28 21:24 ` [Buildroot] [PATCH 8/9] manual: fix typo in abbreviation 'e.g.' Jerzy Grzegorek
2014-03-28 21:24 ` [Buildroot] [PATCH 9/9] manual: fix typo in abbreviation 'i.e.' Jerzy Grzegorek
2014-03-29 8:33 ` [Buildroot] [PATCH 0/9] Documentation cleanup Thomas Petazzoni
2014-03-29 9:52 ` Jerzy Grzegorek
2014-03-29 10:28 ` Thomas Petazzoni [this message]
2014-03-29 10:59 ` Jerzy Grzegorek
2014-03-29 11:05 ` Thomas Petazzoni
2014-03-29 11:17 ` Yann E. MORIN
2014-03-29 11:36 ` Thomas Petazzoni
2014-03-29 11:46 ` Jerzy Grzegorek
2014-03-29 13:28 ` Thomas Petazzoni
2014-03-30 21:52 ` Jerzy Grzegorek
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=20140329112838.0bee5010@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox