Hi Mark.
I've been following this forge experiment with great interest; thanks
for doing this.
I first created this GitHub repo as a way to keep track of the different
status of my patches.
From what I understand, pull requests on forge.sourceware.org can be
removed at any time, so I could lose track of the status of my patches.
I really like forgejo and use it for some of my personal projects. If
you still think there would be benefit in me sending patches to
forge.sourceware.org, please tell me and I'll try.
Regards.
Le 2024-11-19 à 15 h 45, Mark Wielaard a écrit :
Hi,
Random request...
On Tue, Nov 19, 2024 at 11:14:38AM -0500, David Malcolm wrote:
Here's the updated patch and answers below.
(GitHub link if you find it easier for review:
https://github.com/antoyo/libgccjit/pull/5)
Thanks.
Thanks; I looked over the patch via the above link and it looks good to
me for trunk.
Since we now have an experimental forge at https://forge.sourceware.org
would it be an idea to use that for such reviews?
We would love to get feedback on the forge idea (but ideally one based
on Free Software and under community control).
See for some more background:
https://gcc.gnu.org/wiki/ForgeExperiment
You could sign up with your gcc ids (antoyo@gcc... or dmalcolm@gcc...).
Please sent requests for help, feedback (good or bad) to the forge
mailinglist: https://sourceware.org/mailman/listinfo/forge (You don't
need to subscribe unless you want to be part of the forge community.)
Thanks,
Mark
