From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/3] package/uclibc: number patches for 0.9.32.1
Date: Wed, 31 Jul 2013 18:06:22 +0200 [thread overview]
Message-ID: <20130731180622.44197b0a@skate> (raw)
In-Reply-To: <1375275819-29308-1-git-send-email-gustavo@zacarias.com.ar>
Dear Gustavo Zacarias,
On Wed, 31 Jul 2013 10:03:37 -0300, Gustavo Zacarias wrote:
> Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar>
> ---
> ...atch => uclibc-0001-Fix-e500-__fe_nomask_env-use-of-__set_errno.patch} | 0
> ...ch => uclibc-0002-Fix-__libc_epoll_pwait-compile-failure-on-x86.patch} | 0
> ...> uclibc-0003-libc-sysdeps-add-__kernel_long-and-__kernel_ulong.patch} | 0
> .../{uclibc-sparc-errno-fix.patch => uclibc-0004-sparc-errno-fix.patch} | 0
> .../uclibc/0.9.32.1/{uclibc-unshare.patch => uclibc-0005-unshare.patch} | 0
> ...uxthreads-errno-fix.patch => uclibc-0006-linuxthreads-errno-fix.patch} | 0
> 6 files changed, 0 insertions(+), 0 deletions(-)
Commit all three patches. Two things to notice:
* Patchwork didn't detect PATCH 1/3, probably because it only
consisted of git rename, and the patch itself was empty.
* We normally don't accept feature patches in Buildroot. However,
uClibc is really a core component, and their release cycle is slow
(too say the least), so when a feature is upstream, it sometimes
makes sense to backport it. But this should be the exception rather
than the rule.
Thanks!
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2013-07-31 16:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-31 13:03 [Buildroot] [PATCH 1/3] package/uclibc: number patches for 0.9.32.1 Gustavo Zacarias
2013-07-31 13:03 ` [Buildroot] [PATCH 2/3] package/uclibc: add execvpe() backport Gustavo Zacarias
2013-07-31 13:03 ` [Buildroot] [PATCH 3/3] package/uclibc: add mkostemp() backport Gustavo Zacarias
2013-07-31 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=20130731180622.44197b0a@skate \
--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