From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v5 1/1] ktap: new package
Date: Tue, 10 Dec 2013 21:50:31 +0100 [thread overview]
Message-ID: <87vbyw4ei0.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <52A74757.8030100@mind.be> (Arnout Vandecappelle's message of "Tue, 10 Dec 2013 17:54:47 +0100")
>>>>> "Arnout" == Arnout Vandecappelle <arnout@mind.be> writes:
>> Ok, sounds logical.
>> So what is the best comment text? Simply:
>> "foo needs a Linux kernel to be built"
> Sounds good to me. "to be built by buildroot" would be more accurate
> but probably too verbose.
Agreed.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2013-12-10 20:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-10 11:59 [Buildroot] [PATCH v5 1/1] ktap: new package Anders Darander
2013-12-10 12:35 ` Peter Korsgaard
2013-12-10 12:55 ` Anders Darander
2013-12-10 13:01 ` Jeremy Rosen
2013-12-10 13:39 ` Peter Korsgaard
2013-12-10 14:36 ` Thomas De Schampheleire
2013-12-10 14:42 ` Peter Korsgaard
2013-12-10 14:49 ` Thomas De Schampheleire
2013-12-10 16:54 ` Arnout Vandecappelle
2013-12-10 20:50 ` Peter Korsgaard [this message]
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=87vbyw4ei0.fsf@dell.be.48ers.dk \
--to=jacmet@uclibc.org \
--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