From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/5] docs/manual: mention the new post-image mechanism
Date: Wed, 16 Jan 2013 22:42:47 +0100 [thread overview]
Message-ID: <20130116224247.6f94a532@skate> (raw)
In-Reply-To: <201301162106.06305.yann.morin.1998@free.fr>
Dear Yann E. MORIN,
On Wed, 16 Jan 2013 21:06:06 +0100, Yann E. MORIN wrote:
> Thomas, All,
>
> On Wednesday 16 January 2013 Thomas Petazzoni wrote:
> > Signed-off-by: Thomas Petazzoni
> > <thomas.petazzoni@free-electrons.com> ---
> > docs/manual/customize-rootfs.txt | 15 +++++++++++++++
> > 1 file changed, 15 insertions(+)
>
> Why did you split the doc-patch out of the feature-patch?
>
> I would expect that documentation is committed in the same changeset
> as the feature (or bug-fix) it relates to.
Simply because not having the documentation doesn't prevent the feature
from working, but it makes the patch smaller, so easier to review, in
my opinion.
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-01-16 21:42 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-16 19:09 [Buildroot] Post-image script feature and other related fixes Thomas Petazzoni
2013-01-16 19:09 ` [Buildroot] [PATCH 1/5] Add a post-image script mechanism Thomas Petazzoni
2013-01-16 19:22 ` Stefan Fröberg
2013-01-16 20:03 ` Yann E. MORIN
2013-01-16 21:41 ` Thomas Petazzoni
2013-01-16 22:06 ` Yann E. MORIN
2013-01-17 8:14 ` Jeremy Rosen
2013-01-25 18:48 ` Yann E. MORIN
2013-01-29 16:27 ` Luca Ceresoli
2013-01-16 19:09 ` [Buildroot] [PATCH 2/5] docs/manual: mention the new post-image mechanism Thomas Petazzoni
2013-01-16 20:06 ` Yann E. MORIN
2013-01-16 21:42 ` Thomas Petazzoni [this message]
2013-01-25 18:50 ` Yann E. MORIN
2013-01-29 16:27 ` Luca Ceresoli
2013-01-16 19:09 ` [Buildroot] [PATCH 3/5] package/customize: remove Thomas Petazzoni
2013-01-19 12:51 ` Arnout Vandecappelle
2013-01-25 18:35 ` Yann E. MORIN
2013-01-29 16:27 ` Luca Ceresoli
2013-01-16 19:09 ` [Buildroot] [PATCH 4/5] docs/manual: no longer mention the package/customize thing Thomas Petazzoni
2013-01-16 20:10 ` Yann E. MORIN
2013-01-25 18:32 ` Yann E. MORIN
2013-01-29 16:27 ` Luca Ceresoli
2013-01-16 19:09 ` [Buildroot] [PATCH 5/5] docs/manual: slightly reword the solutions to customize rootfs Thomas Petazzoni
2013-01-25 18:31 ` Yann E. MORIN
2013-01-29 16:27 ` Luca Ceresoli
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=20130116224247.6f94a532@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