Automated patch emails for Rust front-end commits

[Arthur Cohen]

Hi everyone,

We recently had a chat with Richi about what the Rust front-end could do
to increase the interactions with the GCC side of our community. Richi
pointed out that it would be good for patches to show up on the mailing
list as they are merged in our development repository, rather than in
batches whenever we send a patchset upstream.

To that end, Marc Poulhiès worked on a new script in our CI testing
which sends patches for every commit that has been merged on GitHub.
You will see these emails with a "[gccrs COMMIT]" subject, to
indicate they've been committed on our side. They will come from the
"gerris.rs@gmail.com" email address which we use for a other things
related to gccrs. Reviews and drive-by comments on these emails are more
than welcome! Please don't hesitate to interact with them and we will
address your reviews.

At the beginning of each week, we will then send these commits again
through a patchset which we'll push directly to trunk. We'll then send
patch emails with a "[COMMITTED]" subject like we've done in the past.

If anyone has anything else they'd like to see us do, please let me 
know! We are happy to work on anything that will increase the 
communication and/or interaction between the Rust side and the GCC side 
of our little front-end.

Kindly,

Arthur
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_0x1B3465B044AD9C65.asc
Type: application/pgp-keys
Size: 3143 bytes
Desc: OpenPGP public key
URL: <https://gcc.gnu.org/pipermail/gcc/attachments/20251111/f31568cf/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature.asc
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <https://gcc.gnu.org/pipermail/gcc/attachments/20251111/f31568cf/attachment.sig>