On 30/6/2023 4:20 pm, Sebastian Huber wrote:
> On 29.06.23 02:20, Chris Johns wrote:
>> On 28/6/2023 3:33 pm, Sebastian Huber wrote:
>>> On 28.06.23 04:37, Chris Johns wrote:
Can you please provide something other than update in the commit message?
If it is to pick up patches on
On 29.06.23 02:20, Chris Johns wrote:
On 28/6/2023 3:33 pm, Sebastian Huber wrote:
On 28.06.23 04:37, Chris Johns wrote:
Can you please provide something other than update in the commit message?
If it is to pick up patches on these gcc release branches then please say so.
This update has
On 28/6/2023 3:33 pm, Sebastian Huber wrote:
> On 28.06.23 04:37, Chris Johns wrote:
>> Can you please provide something other than update in the commit message?
>>
>> If it is to pick up patches on these gcc release branches then please say so.
>
> This update has no particular reason. I just
On 28.06.23 04:37, Chris Johns wrote:
Can you please provide something other than update in the commit message?
If it is to pick up patches on these gcc release branches then please say so.
This update has no particular reason. I just had a bit of time to run my
update script. Ideally there
Can you please provide something other than update in the commit message?
If it is to pick up patches on these gcc release branches then please say so.
Are these versions of the compiler tracking tarfile packages?
Thanks
Chris
On 27/6/2023 8:21 pm, Sebastian Huber wrote:
> ---
>
---
rtems/config/tools/rtems-gcc-10-newlib-head.cfg | 4 ++--
rtems/config/tools/rtems-gcc-12-newlib-head.cfg | 4 ++--
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/rtems/config/tools/rtems-gcc-10-newlib-head.cfg
b/rtems/config/tools/rtems-gcc-10-newlib-head.cfg
index
