From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 02/11] manual: minor fix in patch-policy.txt
Date: Tue, 26 Feb 2013 09:29:07 +0100 [thread overview]
Message-ID: <20130226092907.48b09b41@skate> (raw)
In-Reply-To: <677f6fbb5a9c1994131975c171a285c4335c38d8.1361827174.git.s.martin49@gmail.com>
Dear Samuel Martin,
On Mon, 25 Feb 2013 22:31:22 +0100, Samuel Martin wrote:
> +- If a patch does some package version fixes, this should be documented in the
> +commit message of the patch itself (or the message prepended to the 'diff'
> +itself).
I am not sure to understand this part.
> +* Otherwise, patch files matching +<packagename>-<description>.patch+
> + are applied following the +ls+ command order.
Shouldn't we be enforcing a <packagename>-<number>-<description>.patch
policy, in order to ensure that patches are applied in the right order?
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-02-26 8:29 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-25 21:31 [Buildroot] [pull request v2] Pull request for branch for-master/doc Samuel Martin
2013-02-25 21:31 ` [Buildroot] [PATCH 01/11] manual: fix cross-refs Samuel Martin
2013-02-28 21:38 ` Peter Korsgaard
2013-02-25 21:31 ` [Buildroot] [PATCH 02/11] manual: minor fix in patch-policy.txt Samuel Martin
2013-02-26 8:29 ` Thomas Petazzoni [this message]
2013-02-26 9:44 ` Samuel Martin
2013-02-26 11:01 ` Thomas Petazzoni
2013-02-26 11:15 ` Samuel Martin
2013-02-25 21:31 ` [Buildroot] [PATCH 03/11] manual: misc. post-{build, image} scripts fixes Samuel Martin
2013-02-26 8:30 ` Thomas Petazzoni
2013-02-28 21:39 ` Peter Korsgaard
2013-02-25 21:31 ` [Buildroot] [PATCH 04/11] working-with: board support Samuel Martin
2013-02-26 17:45 ` Arnout Vandecappelle
2013-02-28 21:39 ` Peter Korsgaard
2013-02-25 21:31 ` [Buildroot] [PATCH 05/11] support: add kconfiglib python module Samuel Martin
2013-02-26 20:18 ` Arnout Vandecappelle
2013-02-25 21:31 ` [Buildroot] [PATCH 06/11] support/scripts: add gen-manual-lists.py Samuel Martin
2013-02-25 21:31 ` [Buildroot] [PATCH 07/11] manual: add a make target 'manual-update-lists' Samuel Martin
2013-02-25 21:31 ` [Buildroot] [PATCH 08/11] manual: cleanup appendix.txt Samuel Martin
2013-02-25 21:31 ` [Buildroot] [PATCH 09/11] Makefile: add to the release target a warning about the manual updates Samuel Martin
2013-02-25 21:31 ` [Buildroot] [PATCH 10/11] manual: update generated lists Samuel Martin
2013-02-25 21:31 ` [Buildroot] [PATCH 11/11] Manual: add empty line after header in .mk files Samuel Martin
2013-02-28 21:39 ` Peter Korsgaard
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=20130226092907.48b09b41@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