From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3/3] support/script/scancpan: add option test
Date: Wed, 1 Oct 2014 21:34:02 +0200 [thread overview]
Message-ID: <20141001213402.553f2999@free-electrons.com> (raw)
In-Reply-To: <1412188619-3981-3-git-send-email-francois.perrad@gadz.org>
Dear Francois Perrad,
On Wed, 1 Oct 2014 20:36:59 +0200, Francois Perrad wrote:
> test modules are usually useless on BR
>
> Signed-off-by: Francois Perrad <francois.perrad@gadz.org>
Sorry for asking only now, but can we have a real commit message that
explains what's going on?
Something like:
"""
This commit adds a new -test option to the scancpan script, which
allows to ...
"""
With your current message "test modules are usually useless on BR", I
don't understand what this option does: does it disables test modules?
does it enables it? what does it change compared to the previous
situation?
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-10-01 19:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-01 18:36 [Buildroot] [PATCH 1/3] perl: bump to version 5.20.1 Francois Perrad
2014-10-01 18:36 ` [Buildroot] [PATCH 2/3] perl: add hash Francois Perrad
2014-10-02 19:03 ` Peter Korsgaard
2014-10-01 18:36 ` [Buildroot] [PATCH 3/3] support/script/scancpan: add option test Francois Perrad
2014-10-01 19:34 ` Thomas Petazzoni [this message]
2014-10-03 12:57 ` François Perrad
2014-10-03 13:03 ` Thomas Petazzoni
2014-10-04 12:44 ` Thomas Petazzoni
2014-10-02 19:02 ` [Buildroot] [PATCH 1/3] perl: bump to version 5.20.1 Peter Korsgaard
2014-10-04 12:26 ` Thomas Petazzoni
2014-10-04 12:52 ` François Perrad
2014-10-04 13:05 ` Thomas Petazzoni
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=20141001213402.553f2999@free-electrons.com \
--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 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.