> > I haven't been able to look at a complete log to understand the basis of
> > the report.
> >
> > The mail says to ask here, so here I be. Please advise. I'm not subscribed
> > to this list.
> >
> > Thanks,
> >
> > --jkl
> >
Hi James,
I, personally, use "git format-patch / git send-email" workflow. This is
described in [1] and in man pages of these respective commands. Don't mind
that it is a checklist for glibc -- gcc uses the same process.
[1] https://sourceware.org/glibc/wiki/Contribution%20checklist
HTH,
--
On Thu, 20 Feb 2025 15:05:48 +1300
Maxim Kuvyrkov wrote:
Hi Maxim,
Thank you kindly for your helpful reply. Despite running my own mailserver for
25 years (reluctantly of late because bureaucracy) it seems I still have things
to learn.
> > In gcc_build master-aarch64, after:
> > | gcc pa
ks,
>
> --jkl
>
>
> Begin forwarded message:
>
> Date: Wed, 19 Feb 2025 15:10:38 +0000 (UTC)
> From: ci_not...@linaro.org
> To: jklow...@schemamania.org
> Subject: [Linaro-TCWG-CI] gcc patch #106762: Failure on aarch64
>
>
> Dear contributor,
>
>
9 Feb 2025 15:10:38 + (UTC)
From: ci_not...@linaro.org
To: jklow...@schemamania.org
Subject: [Linaro-TCWG-CI] gcc patch #106762: Failure on aarch64
Dear contributor,
Our automatic CI has detected problems related to your patch(es).
Please find some details below.
In gcc_build master-aarch
