From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] uclibc: add a missing function member to siginfo.h
Date: Tue, 28 Jan 2014 22:25:48 +0100 [thread overview]
Message-ID: <20140128222548.1eee4176@skate> (raw)
In-Reply-To: <52CFC72A.3010907@imgtec.com>
Dear Vicente Olivert Riera,
On Fri, 10 Jan 2014 10:10:50 +0000, Vicente Olivert Riera wrote:
> So I understand that your suggestion is to not apply uClibc patches in
> Buildroot anymore and just disable the packages (the ones that are
> failing) for the affected uClibc versions, and keep them enabled when
> the uClibc daily snapshot is selected. Am I right?
This would be my preferred solution yes. This way, people would
probably realize how broken the uClibc release process is, and would
maybe be encouraged to work with upstream.
I've added this topic as a discussion item for the upcoming Buildroot
Developers meeting.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-01-28 21:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-08 17:32 [Buildroot] [PATCH 1/2] uclibc: add a missing function member to siginfo.h Vicente Olivert Riera
2014-01-08 17:32 ` [Buildroot] [PATCH 2/2] uclibc: Make __SIGEV_PAD_SIZE to take __WORDSIZE into account Vicente Olivert Riera
2014-10-12 7:46 ` Peter Korsgaard
2014-01-09 2:40 ` [Buildroot] [PATCH 1/2] uclibc: add a missing function member to siginfo.h Thomas Petazzoni
2014-01-09 9:46 ` Vicente Olivert Riera
2014-01-10 7:36 ` Thomas Petazzoni
2014-01-10 10:10 ` Vicente Olivert Riera
2014-01-28 21:25 ` Thomas Petazzoni [this message]
2014-10-11 15:16 ` [Buildroot] [PATCH] rt-tests: enable on MIPS uClibc again Arnout Vandecappelle
2014-10-12 7:47 ` Peter Korsgaard
2014-10-12 7:46 ` [Buildroot] [PATCH 1/2] uclibc: add a missing function member to siginfo.h 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=20140128222548.1eee4176@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