On Feb 6, 2022, at 22:23, Colin Campbell wrote:
>
> For my guidance, I'd be grateful if the community would correct or amplify
> the following recap of the patch handling process.
>
Colin, I think you summed it up well and I agree with Lukas' additions.
Thanks,
—
Dan
On 2022-02-07 02:07, Lukas-Fabian Moser wrote:
Hi Colin,
forgive me for butting in as someone who has made very few
contributions (but followed some of the discussions quite closely over
the last few years):
So what I'm trying to say is: A task that seems like a trivial cron
job 95% of
changed the flow significantly. The patch scheduling function, and
again, I only describe my outsider's understanding, seems to have
become a cron job running in wetware. It would seem more efficient to
implement a script which would take the same set of decisions, update
labels, and run
changed the
flow significantly. The patch scheduling function, and again, I only
describe my outsider's understanding, seems to have become a cron job
running in wetware. It would seem more efficient to implement a script
which would take the same set of decisions, update labels, and run
