From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/3] libite: new package
Date: Sun, 16 Oct 2016 18:06:36 +0200 [thread overview]
Message-ID: <20161016180636.372508ee@free-electrons.com> (raw)
In-Reply-To: <20161013034247.21603-1-bluemrp9@gmail.com>
Hello,
On Wed, 12 Oct 2016 20:42:45 -0700, Ryan Coe wrote:
> Signed-off-by: Ryan Coe <bluemrp9@gmail.com>
> ---
> DEVELOPERS | 3 +++
> package/Config.in | 1 +
> package/libite/Config.in | 15 +++++++++++++++
> package/libite/libite.hash | 2 ++
> package/libite/libite.mk | 14 ++++++++++++++
> 5 files changed, 35 insertions(+)
> create mode 100644 package/libite/Config.in
> create mode 100644 package/libite/libite.hash
> create mode 100644 package/libite/libite.mk
The DEVELOPERS change should have been part of a separate patch. We do
this to ease the work of backporting changes in older Buildroot
releases (the changes in DEVELOPERS file tend to cause a large number
of conflicts).
I also rewrapped the Config.in help text, and adjusted the license
information to be more precise.
With those changes: applied. Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2016-10-16 16:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-13 3:42 [Buildroot] [PATCH 1/3] libite: new package Ryan Coe
2016-10-13 3:42 ` [Buildroot] [PATCH 2/3] inadyn: do not install default conf file Ryan Coe
2016-10-16 16:11 ` Thomas Petazzoni
2016-10-13 3:42 ` [Buildroot] [PATCH 3/3] inadyn: bump to version 2.0 Ryan Coe
2016-10-16 16:14 ` Thomas Petazzoni
2016-10-16 16:06 ` Thomas Petazzoni [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=20161016180636.372508ee@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox