[lng-odp] api-next branch force updated

Hello, api-next branch is forced update to current master. Please audjust that in your PR. Backup is here: https://github.com/muvarov/odp/tree/api-next_1.18_backup Thank you, Maxim.

Re: [lng-odp] API-next branch

>> -Original Message- >> From: lng-odp [mailto:lng-odp-boun...@lists.linaro.org] On Behalf Of Bill >> Fischofer >> Sent: Wednesday, October 25, 2017 6:53 PM >> To: Dmitry Eremin-Solenikov <dmitry.ereminsoleni...@linaro.org> >> Cc: lng-odp-forw

Re: [lng-odp] API-next branch

hursday, October 26, 2017 10:30 AM > To: Savolainen, Petri (Nokia - FI/Espoo) <petri.savolai...@nokia.com> > Cc: Bill Fischofer <bill.fischo...@linaro.org>; Dmitry Eremin-Solenikov > <dmitry.ereminsoleni...@linaro.org>; lng-odp-forward > <lng-odp@lists.linaro.org> >

Re: [lng-odp] API-next branch

er 26, 2017 10:30 AM To: Savolainen, Petri (Nokia - FI/Espoo) <petri.savolai...@nokia.com> Cc: Bill Fischofer <bill.fischo...@linaro.org>; Dmitry Eremin-Solenikov <dmitry.ereminsoleni...@linaro.org>; lng-odp-forward <lng-odp@lists.linaro.org> Subject: Re: [lng-odp] API-next b

Re: [lng-odp] API-next branch

gt; small delta). > > -Petri > > > > > -Original Message- > > From: lng-odp [mailto:lng-odp-boun...@lists.linaro.org] On Behalf Of > Bill > > Fischofer > > Sent: Wednesday, October 25, 2017 6:53 PM > > To: Dmitry Eremin-Solenikov <dmitry.ere

Re: [lng-odp] API-next branch

-Petri > -Original Message- > From: lng-odp [mailto:lng-odp-boun...@lists.linaro.org] On Behalf Of Bill > Fischofer > Sent: Wednesday, October 25, 2017 6:53 PM > To: Dmitry Eremin-Solenikov <dmitry.ereminsoleni...@linaro.org> > Cc: lng-odp-forward <lng-odp@lists.linaro.org&g

Re: [lng-odp] API-next branch

I'm all for using topic branches, especially since we've switched to GitHub and most contributors are now familiar with it and using pull requests rather than raw patches sent to the mailing list. The whole reason for api-next was to separate in-progress API changes from regular maintenance

[lng-odp] API-next branch

Hello, I tried to actually check, which patches are sitting in the api-next. And actually I failed to do that in a timely manner. git cherry produces a list of patches, that contains a lot of patches, which already landed to the master. Quick proposal would be to stop using api-next as a

Re: [lng-odp] api-next branch broken?

On Sat, May 20, 2017 at 1:38 PM, Maxim Uvarov wrote: > On 05/20/17 01:07, Bill Fischofer wrote: > > Something is clearly going on as I'm seeing the pktio/pktio_ipc_run.sh > > script suddenly start failing for completely unrelated changes. > > > > > Can you reproduce it

Re: [lng-odp] api-next branch broken?

On 05/20/17 01:07, Bill Fischofer wrote: > Something is clearly going on as I'm seeing the pktio/pktio_ipc_run.sh > script suddenly start failing for completely unrelated changes. > Can you reproduce it manually? I can not reproduce it locally and here looks like it passed for the latest code

Re: [lng-odp] api-next branch broken?

Something is clearly going on as I'm seeing the pktio/pktio_ipc_run.sh script suddenly start failing for completely unrelated changes. On Fri, May 19, 2017 at 5:02 PM, Dmitry Eremin-Solenikov < dmitry.ereminsoleni...@linaro.org> wrote: > Since one of last updates I'm receiving timeouts from

[lng-odp] api-next branch broken?

Since one of last updates I'm receiving timeouts from Travis CI because some tests run silently taking too much time to complete. -- With best wishes Dmitry

Re: [lng-odp] API-NEXT branch is broken

On 13 January 2016 at 15:33, Bill Fischofer wrote: > If we can eliminate a dependency that seems like another reason to use the > .svgs directly. I really don't see the need for PDF support since few are > going to be printing manuals these days. > Agree, I am hoping

Re: [lng-odp] API-NEXT branch is broken

Probably we need to add convert (imagemagic package?) check to ./configure. Maxim. On 01/13/2016 19:01, Mike Holmes wrote: Have you installed the DEPENDENCIES for building the docs ? Did you just make or "make distcheck" On 13 January 2016 at 10:58, Bala Manoharan

Re: [lng-odp] API-NEXT branch is broken

On 13 January 2016 at 14:31, Maxim Uvarov wrote: > Probably we need to add convert (imagemagic package?) check to ./configure. > It is there, what has changed is that it apparently gets required even if you dont build docs. As we move to direct use of .svg I can delete

Re: [lng-odp] API-NEXT branch is broken

If we can eliminate a dependency that seems like another reason to use the .svgs directly. I really don't see the need for PDF support since few are going to be printing manuals these days. On Wed, Jan 13, 2016 at 2:11 PM, Mike Holmes wrote: > > > On 13 January 2016 at

Re: [lng-odp] API-NEXT branch is broken

On Wed, Jan 13, 2016 at 2:35 PM, Mike Holmes wrote: > > > On 13 January 2016 at 15:33, Bill Fischofer > wrote: > >> If we can eliminate a dependency that seems like another reason to use >> the .svgs directly. I really don't see the need for

Re: [lng-odp] API-NEXT branch is broken

Have you installed the DEPENDENCIES for building the docs ? Did you just make or "make distcheck" On 13 January 2016 at 10:58, Bala Manoharan wrote: > Hi, > > The api-next branch is broken after merge from master. > convert atomic_queue.svg atomic_queue.png >

[lng-odp] API-NEXT branch is broken

Hi, The api-next branch is broken after merge from master. convert atomic_queue.svg atomic_queue.png /bin/bash: convert: command not found make[2]: *** [atomic_queue.png] Error 127 Regards, Bala ___ lng-odp mailing list lng-odp@lists.linaro.org