From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v4] mtree: new package
Date: Thu, 28 Mar 2019 21:59:59 +0100 [thread overview]
Message-ID: <87ef6qlnow.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20190328210043.41fc2c0d@windsurf> (Thomas Petazzoni's message of "Thu, 28 Mar 2019 21:00:43 +0100")
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@bootlin.com> writes:
> On Thu, 28 Mar 2019 19:13:16 +0100
> Arnout Vandecappelle <arnout@mind.be> wrote:
>> > I think I will give option 2 a try. Sounds like a nice solution :-)
>>
>> To be honest, I'm more inclined to remove the -U completely and add an
>> autobuilder exception... I don't believe we have to go too far to work around
>> bugs in old toolchains.
> I'm fine with this as well. It means we would no longer support glibc
> 2.19 anymore.
Didn't you just last month argue against removing support for glibc <
2.19 support (the runc security fix):
http://lists.busybox.net/pipermail/buildroot/2019-February/244056.html
I don't have a problem dropping support for ancient toolchains when they
add too much complexity, but the lack of large file support is mtree is
probably not really reason enough.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2019-03-28 20:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-26 14:24 [Buildroot] [PATCH v4] mtree: new package Esben Haabendal
2019-03-27 19:18 ` Thomas Petazzoni
2019-03-27 22:28 ` Esben Haabendal
2019-03-28 11:14 ` Thomas Petazzoni
2019-03-28 15:14 ` Esben Haabendal
2019-03-28 18:13 ` Arnout Vandecappelle
2019-03-28 20:00 ` Thomas Petazzoni
2019-03-28 20:59 ` Peter Korsgaard [this message]
2019-03-28 21:53 ` Thomas Petazzoni
2019-03-29 9:31 ` Arnout Vandecappelle
2019-03-29 9:35 ` Thomas Petazzoni
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=87ef6qlnow.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.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.