Am 20.01.23 um 06:21 schrieb Chris Johns:
On 20/1/2023 1:50 am, Christian MAUDERER wrote:
Am 19.01.23 um 15:42 schrieb Gedare Bloom:
Nice. I would like some time to look at this and think about it a
little more. What would be the plan for removing this capability? Will
it leave any artifacts be
On 20/1/2023 1:50 am, Christian MAUDERER wrote:
> Am 19.01.23 um 15:42 schrieb Gedare Bloom:
>> Nice. I would like some time to look at this and think about it a
>> little more. What would be the plan for removing this capability? Will
>> it leave any artifacts behind in the RTEMS github mirror?
>
Am 19.01.23 um 15:42 schrieb Gedare Bloom:
Nice. I would like some time to look at this and think about it a
little more. What would be the plan for removing this capability? Will
it leave any artifacts behind in the RTEMS github mirror?
As soon as we want to get rid of the scripts again (becau
On 19.01.23 15:42, Gedare Bloom wrote:
Nice. I would like some time to look at this and think about it a
little more. What would be the plan for removing this capability? Will
it leave any artifacts behind in the RTEMS github mirror?
It seems by default stuff is kept for about 90 days:
https:/
Nice. I would like some time to look at this and think about it a
little more. What would be the plan for removing this capability? Will
it leave any artifacts behind in the RTEMS github mirror?
On Mon, Jan 16, 2023 at 6:42 AM Christian Mauderer
wrote:
>
> Hello,
>
> some weeks ago I created a Gi
Hello,
some weeks ago I created a GitHub Actions based CI script that we
(embedded brains) wanted to use to test patches (see
https://github.com/embedded-brains/rtems/tree/ci). I don't think much of
the RTEMS community noted these. I would like to suggest adding the
scripts to the official RTEMS r
