From: Peter Korsgaard <jacmet@sunsite.dk>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit] uclibc: add upstream 0.9.33 fixes
Date: Fri, 06 Sep 2013 22:53:53 +0200 [thread overview]
Message-ID: <87ppsl1xjy.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20130906163551.571faf5c@skate> (Thomas Petazzoni's message of "Fri, 6 Sep 2013 16:35:51 +0200")
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
Hi,
>> Drop uclibc-0002-Add-definition-of-MSG_WAITFORONE-and-MSG_CMSG_CMSG_CLOEXE.patch
>> as that is a subset of uclibc-0035-socket.h-pull-socket_type.h-from-eglibc.patch
Thomas> Shouldn't we switch to using the git version of uClibc instead of
Thomas> carrying 40+ patches? The uClibc project seems to have issues getting
Thomas> releases out, maybe we should just use their git version, and bump it
Thomas> from time to time when appropriate?
Yes, Perhaps. When I started this, I only thought I would add 2-3
patches to fix the eventfd issue - but looking closer, the other patches
seemed worthwhile as well.
We do carry a few patches that aren't (yet?) part of upstream git on the
0.9.33 branch, so it wouldn't get rid of all patches (but most). Another
potential issue is that git almost becomes a hard buildroot dependency,
but that's probably not a big problem.
What do others say?
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2013-09-06 20:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-06 13:28 [Buildroot] [git commit] uclibc: add upstream 0.9.33 fixes Peter Korsgaard
2013-09-06 14:35 ` Thomas Petazzoni
2013-09-06 20:53 ` Peter Korsgaard [this message]
2013-09-09 16:26 ` Arnout Vandecappelle
-- strict thread matches above, loose matches on Subject: below --
2012-02-16 11:20 [Buildroot] [git commit] uClibc: " 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=87ppsl1xjy.fsf@dell.be.48ers.dk \
--to=jacmet@sunsite.dk \
--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