* [Buildroot] [autobuild.buildroot.net] Your build results for 2019-07-01 [not found] <5d1af309.1c69fb81.cf999.ba7eSMTPIN_ADDED_MISSING@mx.google.com> @ 2019-07-02 20:36 ` Petr Vorel 2019-07-03 22:04 ` Peter Korsgaard 0 siblings, 1 reply; 2+ messages in thread From: Petr Vorel @ 2019-07-02 20:36 UTC (permalink / raw) To: buildroot Hi, > Hello, > This is the list of Buildroot build failures that occured on > 2019-07-01, and for which you are a registered architecture developer > or package developer. Please help us improving the quality of > Buildroot by investigating those build failures and sending patches to > fix them. Thanks! > Results for the 'master' branch > =============================== > Build failures related to your packages: > sh4 | iputils-20190515 | http://autobuild.buildroot.net/results/e2ad49ca3b59c5d4b0fb883fc3a79483ba023428 > microblazeel | iputils-20190515 | http://autobuild.buildroot.net/results/53c8354aba24ac99a532d3fc50132e4d5eeb1ff6 > mips | iputils-20190515 | http://autobuild.buildroot.net/results/cf3c2016be18882713a70baa367ef6836df207c1 > sh4 | iputils-20190515 | http://autobuild.buildroot.net/results/c891df50b2ca01c969e5275ca92d74ce861af8ee > arm | iputils-20190515 | http://autobuild.buildroot.net/results/754179740a63d4c34480804f2b733f687a7128dd At least some of these are fixed in next branch. What is the policy? Can be individual commits cherrypicked? Or does it need to wait till next release? Kind regards, Petr ^ permalink raw reply [flat|nested] 2+ messages in thread
* [Buildroot] [autobuild.buildroot.net] Your build results for 2019-07-01 2019-07-02 20:36 ` [Buildroot] [autobuild.buildroot.net] Your build results for 2019-07-01 Petr Vorel @ 2019-07-03 22:04 ` Peter Korsgaard 0 siblings, 0 replies; 2+ messages in thread From: Peter Korsgaard @ 2019-07-03 22:04 UTC (permalink / raw) To: buildroot >>>>> "Petr" == Petr Vorel <petr.vorel@gmail.com> writes: > Hi, >> Hello, >> This is the list of Buildroot build failures that occured on >> 2019-07-01, and for which you are a registered architecture developer >> or package developer. Please help us improving the quality of >> Buildroot by investigating those build failures and sending patches to >> fix them. Thanks! >> Results for the 'master' branch >> =============================== >> Build failures related to your packages: >> sh4 | iputils-20190515 | http://autobuild.buildroot.net/results/e2ad49ca3b59c5d4b0fb883fc3a79483ba023428 >> microblazeel | iputils-20190515 | http://autobuild.buildroot.net/results/53c8354aba24ac99a532d3fc50132e4d5eeb1ff6 >> mips | iputils-20190515 | http://autobuild.buildroot.net/results/cf3c2016be18882713a70baa367ef6836df207c1 >> sh4 | iputils-20190515 | http://autobuild.buildroot.net/results/c891df50b2ca01c969e5275ca92d74ce861af8ee >> arm | iputils-20190515 | http://autobuild.buildroot.net/results/754179740a63d4c34480804f2b733f687a7128dd > At least some of these are fixed in next branch. What is the policy? Can be > individual commits cherrypicked? Or does it need to wait till next release? I take it you mean next branch / release of iputils? Sending cherry picks of specific fixes is fine. -- Bye, Peter Korsgaard ^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2019-07-03 22:04 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <5d1af309.1c69fb81.cf999.ba7eSMTPIN_ADDED_MISSING@mx.google.com>
2019-07-02 20:36 ` [Buildroot] [autobuild.buildroot.net] Your build results for 2019-07-01 Petr Vorel
2019-07-03 22:04 ` Peter Korsgaard
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox