On Thu, 20 Feb 2025 15:05:48 +1300
Maxim Kuvyrkov <maxim.kuvyr...@linaro.org> 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 patch https://patchwork.sourceware.org/patch/106762
> 
> Looking at the above patchwork entry, I see that your patch "COBOL
> v3: 3/14 80K bld: config and build machinery" was not detected as
> part of the series [1], which means it was applied without the
> prerequisite 1/14 and 2/14 patches.  That's the reason for the
> failure.
> 
> [1] https://patchwork.sourceware.org/project/gcc/list/?series=44237
> 
> Looking at your whole submission [2], I see that patchwork sees each
> patch as its own series, so our CI will test them individually.  I'm,
> actually, surprised that only patch 3/14 fails to build -- the rest
> pass the CI.  I would have expected all but 1/14 to fail.

I did receive a few other reports.  Pehaps they were applied in parallel, and 
those that happened to be sequenced after 1/14 succeeded.  That would make 
sense to me.  

The problem would seem to be that I don't know what a patch series is.  

My patches are produced in the simplest way imaginable for someone who uses git 
while wearing oven mitts to avoid scorching.  I have a script that runs "git 
diff" for a set of files, and one to convert that into a mail message. Then I 
use sylpheed to send each one in turn.  (I could use nmh but I'm less 
comfortable with that, for sending.  Nothing beats nmh for searching mail.)  

I think you are going to tell me that some git magic will link those together 
as a series.  Possibly a gcc git script.  I haven't tried to connect git to 
mail because the git boxes aren't set up to send/receive mail.  I've been told 
that's unnecessary (and/or easy to rememdy) but so far haven't gotten over the 
hump.  

If you would nudge me in the right direction, perhaps I can DTRT.  

Many thanks for your time.  

Regards, 

--jkl
_______________________________________________
linaro-toolchain mailing list -- linaro-toolchain@lists.linaro.org
To unsubscribe send an email to linaro-toolchain-le...@lists.linaro.org

Reply via email to