gcc ci continue by @cooljeanius

[talregev]

continue work of my linux ci by @cooljeanius
cooljeanius#2

[cooljeanius]

(To be clear I'm not submitting this myself because I am adhering to the norms against submitting PRs here; I only submitted one against the submitter's fork because that was a fork, and not this mirror)

[jwakely]

It's not just a "norm" to not submit here, it's completely pointless because nobody involved with the gcc project has any control of this repo and can't merge these pull requests anyway.

[talregev]

I already send a patch to gcc for the ci and my PR.
They didn't respond.
Doing a PR to here is not pointless.
As you can see, because of of my PR to here, @cooljeanius take my work and continue and improve it.
So even if gcc official don't look at this repo, other from gcc community does. And that how you can share knowledge.

[cooljeanius]

It's not just a "norm" to not submit here, it's completely pointless because nobody involved with the gcc project has any control of this repo and can't merge these pull requests anyway.

Yes, that's why I did 2b9778c. I didn't mean to diminish the pointlessness of submitting here by referring to the discouragement against doing so as a "norm", that was just the first word that came to mind.

[frederick-vs-ja]

I wonder whether it's possible to add some github-actions to transform a PR on gcc-mirror to a mail to the GCC mailing list.

[cooljeanius]

I wonder whether it's possible to add some github-actions to transform a PR on gcc-mirror to a mail to the GCC mailing list.

That's what the git project does with gitgitgadget, but that would require someone to get it set up here: https://github.com/gitgitgadget/gitgitgadget

[jwakely]

There are no admins for this repo. My guess is GitHub set it up but they deny it!

[jwakely]

Also many of the pull requests are complete junk, like trying to merge all of trunk into the gcc-10 branch or similar nonsense.