From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3/3] busybox 1.18.3: add patches for klogd and menuconfig
Date: Thu, 10 Mar 2011 13:57:56 +0100 [thread overview]
Message-ID: <20110310135756.1031efb0@surf> (raw)
In-Reply-To: <1299759904-22003-3-git-send-email-gustavo@zacarias.com.ar>
Hello,
On Thu, 10 Mar 2011 09:25:04 -0300
Gustavo Zacarias <gustavo@zacarias.com.ar> wrote:
> Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar>
> ---
> .../busybox-1.18.3/busybox-1.18.3-klogd.patch | 45 ++++++++++++++++++++
> .../busybox-1.18.3/busybox-1.18.3-menuconfig.patch | 11 +++++
> 2 files changed, 56 insertions(+), 0 deletions(-)
> create mode 100644 package/busybox/busybox-1.18.3/busybox-1.18.3-klogd.patch
> create mode 100644 package/busybox/busybox-1.18.3/busybox-1.18.3-menuconfig.patch
Is it really necessary to add Busybox patches all the time, since they
got deprecated pretty quickly by newer releases ? I mean, at the time
of the Buildroot release, it of course make sense to have the latest
Busybox release with the latest fixes, but during the development
phase, is it really useful ?
Of course, if you already do it for other purposes, that's just fine.
I'm just wondering.
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:[~2011-03-10 12:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-10 12:25 [Buildroot] [PATCH 1/3] xorg-server: point localstatedir to /var Gustavo Zacarias
2011-03-10 12:25 ` [Buildroot] [PATCH 2/3] xz: bump to version 5.0.1 Gustavo Zacarias
2011-03-10 13:39 ` Peter Korsgaard
2011-03-10 12:25 ` [Buildroot] [PATCH 3/3] busybox 1.18.3: add patches for klogd and menuconfig Gustavo Zacarias
2011-03-10 12:57 ` Thomas Petazzoni [this message]
2011-03-10 13:26 ` Peter Korsgaard
2011-03-10 13:41 ` Peter Korsgaard
2011-03-10 13:39 ` [Buildroot] [PATCH 1/3] xorg-server: point localstatedir to /var Peter Korsgaard
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=20110310135756.1031efb0@surf \
--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.