I will vote for that! Best Regards Peter
On Wed, 20 Feb 2019 at 08:58, Luca Ceresoli <[email protected]> wrote: > Hi Jean-Francois, > > On 19/02/19 17:03, Jean-Francois Dagenais wrote: > > There is a discussion started here: > > > https://github.com/Xilinx/meta-xilinx/pull/11/commits/2a00ba8b3e052732eb1c714bebc6f247aa474628#r258102571 > > about the new conflicts around libwayland-egl being provided/installed > by both the libmali-xlnx recipe and the default wayland recipe from poky. > > > > It would be nice to continue the discussion and the proposed patches on > github directly... as teams do in 2019... wink wink! :P > > > > Is Xilinx working on this? > > > > Another suggestion: it would help if Xilinx could push --force to say a > "master-next" branch so we can detect whether we should hack things on our > own or if Xilinx is working on some of the issues we experience between > releases. > > Yes!! > > "Release early, release often" would make working with the Xilinx code > more productive. > > The current workflow is that at some discrete points in time Xilinx > pushes a big pile of patches, so I have to plan some relevant time to: > stop my regular work, rebase on the new Xilinx branches, see what broke > in my code, fix or workaround or redo it, test, repeat, and finally get > back to work a few days/weeks later. > > Discussing patches in a public place would even more allow people here > to improve the code before it goes on master, as opposed to fixing it > after the facts. It has been done in the past for some patches, it > should be done on a regular basis. > > My 2c, > -- > Luca > -- > _______________________________________________ > meta-xilinx mailing list > [email protected] > https://lists.yoctoproject.org/listinfo/meta-xilinx >
-- _______________________________________________ meta-xilinx mailing list [email protected] https://lists.yoctoproject.org/listinfo/meta-xilinx
