You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi.
Going forward, would it be possible to 'label' any commits or issues targeting the C implementation?
This would greatly help in keeping in sync any ports of the C implementation that aim to track as close as possible the original C source here.
I forked RyuCsharp to create Ryu.NET and have been able to port over two bugfixes that postdate the creation of RyuCsharp.
Thanks
N
The text was updated successfully, but these errors were encountered:
I'm not sure either how notifications would work and even if it's possible.
However, I was thinking more along the terms of simply using labels. That way the commits to the C source would be easily marked. Of course one would have to manually scan the issues periodically but that doesn't seem like a blocker
Thanks
EDIT : Oops, I've just seen that you already have labels.
Hi.
Going forward, would it be possible to 'label' any commits or issues targeting the C implementation?
This would greatly help in keeping in sync any ports of the C implementation that aim to track as close as possible the original C source here.
I forked RyuCsharp to create Ryu.NET and have been able to port over two bugfixes that postdate the creation of RyuCsharp.
Thanks
N
The text was updated successfully, but these errors were encountered: