From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] Build failure with 2017.05.1
Date: Wed, 19 Jul 2017 21:38:21 +0200 [thread overview]
Message-ID: <87eftc5iaa.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20170719210932.59467c37@windsurf> (Thomas Petazzoni's message of "Wed, 19 Jul 2017 21:09:32 +0200")
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
Hi,
> We definitely don't want the bump to v3.3.0 in the maintenance branch,
> unless there are security fixes associated.
> However, I think we want to do in 2017.02.x and 2017.05.x what we did
> in master: remove all Github patch downloads, and put the patches in
> the tree instead. For most of the packages, I believe the commits can
> be cherry-picked from master. A few packages will need specific
> adjustments though.
> Peter, do you agree?
Yes, I'll get to it once I'm done with build testing the current pile of
backports.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2017-07-19 19:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-19 18:06 [Buildroot] Build failure with 2017.05.1 Carlos Santos
2017-07-19 19:09 ` Thomas Petazzoni
2017-07-19 19:38 ` Peter Korsgaard [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=87eftc5iaa.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox