On Tue, Apr 28, 2020, 7:28 PM Chris Johns wrote:
> Hello,
>
> We are down to 4 remaining tickets. Many thanks to everyone for all the
> hard work getting to this point. It is appreciated.
>
> The remaining tickets need to be closed or moved before I can branch the
> repos. The milestone page is
On 29/4/20 6:00 pm, Chris Johns wrote:
Also I have currently backed away from a full markdown for the generated
README.txt. It was creating some issues that require more work than is
needed and it is not critical. It can be revisited as part of the on
going support work.
After saying I would
On 30/4/20 1:35 pm, Gedare Bloom wrote:
Tickets
---
New:
https://devel.rtems.org/ticket/3962
I will not be involved in this ticket or driving it and will wait for it
to be closed or moved before we branch. Please help.
I will take care of this, but I don't see it as a blocker for
On Tue, Apr 28, 2020 at 6:28 PM Chris Johns wrote:
>
> Hello,
>
> We are down to 4 remaining tickets. Many thanks to everyone for all the
> hard work getting to this point. It is appreciated.
>
> The remaining tickets need to be closed or moved before I can branch the
> repos. The milestone page
On 29/4/20 3:57 pm, Sebastian Huber wrote:
On 29/04/2020 02:28, Chris Johns wrote:
Release Change Notes
Joel has asked for a high level list of changes to be added to the
release information. He would like this to be a community effort.
We have the detailed release
On 29/04/2020 02:28, Chris Johns wrote:
Release Change Notes
Joel has asked for a high level list of changes to be added to the
release information. He would like this to be a community effort.
We have the detailed release notes created from the Trac tickets for
the
Hello,
We are down to 4 remaining tickets. Many thanks to everyone for all the
hard work getting to this point. It is appreciated.
The remaining tickets need to be closed or moved before I can branch the
repos. The milestone page is ...
https://devel.rtems.org/milestone/5.1
... so please
On 02/04/2020 11:10, Chris Johns wrote:
> On 2020-04-02 20:02, Christian Mauderer wrote:
>> Hello Chris,
>>
>> I don't think that littlevgl is such an essential or stable package yet.
>
> Sure.
>
>> Currently I know of exactly one project using this repository and that's
>> only because I added
On 2020-04-02 20:02, Christian Mauderer wrote:
Hello Chris,
I don't think that littlevgl is such an essential or stable package yet.
Sure.
Currently I know of exactly one project using this repository and that's
only because I added it.
I have used it successfully however not on RTEMS. It
Hello Chris,
I don't think that littlevgl is such an essential or stable package yet.
Currently I know of exactly one project using this repository and that's
only because I added it.
Best regards
Christian
On 02/04/2020 11:00, Chris Johns wrote:
> Hi,
>
> All OK and thanks for letting us
Hi,
All OK and thanks for letting us know.
I am not sure littlevgl is in the release. Maybe it should be?
I am picking up packages via the RSB.
Chris
On 2020-04-02 19:03, Christian Mauderer wrote:
Hello Chris,
sorry, I missed that mail this morning. I pushed a small patch to
Hello Chris,
sorry, I missed that mail this morning. I pushed a small patch to
rtems-littlevgl that fixes a build problem with python3.
I hope I didn't make problems with that.
Best regards
Christian
On 02/04/2020 01:31, Chris Johns wrote:
> Hello,
>
> Please read if you have commit access.
Hello,
Please read if you have commit access.
I am cleaning up a few issues like the release README.txt to match
moving all the released source in to `sources`, then updating the
documentation to reference this and then I will create a 5.0.0-m2004
snapshot.
After this I will be looking to
13 matches
Mail list logo
