From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2 v3] linux/tools: make it a real, separate package
Date: Thu, 22 Sep 2016 20:17:05 +0200 [thread overview]
Message-ID: <87vaxnol3y.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20160922201419.09e59aeb@free-electrons.com> (Thomas Petazzoni's message of "Thu, 22 Sep 2016 20:14:19 +0200")
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
Hi,
> No problem, I was definitely not trying to blame. Just saying that this
> patch series has been around for a while. In this case, if nobody
> commented or proposed a better solution, and the proposed solution
> looks good enough to me, then I commit. Keeping things forever in
> patchwork is not very good to encourage contributions.
And that is how it should be, thanks for taking care of the backlog!
> In the worst case, if there are comments and suggestions when applying
> the patches, it's never too late to rework what has been merged.
Indeed!
--
Venlig hilsen,
Peter Korsgaard
next prev parent reply other threads:[~2016-09-22 18:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-06 14:29 [Buildroot] [PATCH 0/2 v3] linux/tools: move to their own package (branch yem/linux-tools) Yann E. MORIN
2016-09-06 14:29 ` [Buildroot] [PATCH 1/2 v3] linux/tools: make it a real, separate package Yann E. MORIN
2016-09-22 10:51 ` Thomas Petazzoni
2016-09-22 16:33 ` Yann E. MORIN
2016-09-22 14:58 ` Peter Korsgaard
2016-09-22 17:49 ` Thomas Petazzoni
2016-09-22 18:01 ` Peter Korsgaard
2016-09-22 18:14 ` Thomas Petazzoni
2016-09-22 18:17 ` Peter Korsgaard [this message]
2016-09-06 14:29 ` [Buildroot] [PATCH 2/2 v3] docs/manual: update the linux tools section Yann E. MORIN
2016-09-22 10:56 ` 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=87vaxnol3y.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.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