On 2024-09-19, at 03:25:16 -0700, Xiyue Deng wrote:
I'd like to propose to enable Salsa CI for Team Emacsen packages. I
have been running Salsa CI in some of my forks and it serves well as
another pair of eyes for finding and debugging issues, e.g. when
debugging reproducible build issue on flycheck, enabling diffoscope was
very helpful (though it didn't fully fix the issue but that is another story.) Also, it being available without local configuration is great
for new comers before they set up the local build environments, which is optional.
So, I'd like to gather some feedback from folks: how do you think of
enabling Salsa CI for all? Or maybe selective enable it for core
packages or on demand as a start?
I think it's useful, and I've enabled it for some packages:
* emacs-buttercup
* maildir-utils
* muttrc-mode-el
* mutt-alias-el
but I'd be more inclined to enable it on a case-by-case.
J.
-----BEGIN PGP SIGNATURE-----
iQIzBAABCgAdFiEEbB20U2PvQDe9VtUXKYasCr3xBA0FAmbsFOIACgkQKYasCr3x BA2pZQ//db6WM+DcpNX/HU5V97ShH+AXQ65nwJn5qpwOKy+VFx8gPE6HONdC/+GE FxSSppFK6F0y7zhaxW1Urg5+votoR9peOoNDH/AfAO70LB/Uns7mj8IGipMc9nXc Z71SeOk62aB46Py0tpG2GN8BWsyZkUdVnXUbSFbjaNHPqUdyv3pvUqtp3xnu18Rs PzbZYCerDSkvf3e/y5rafVN2dZLDvJ+6V5wNGfSsRtH+wJs1JUtMTBck2xz7qnfE AUpLlfaeCKVjrLAyFQW+hvW8sI6sv0u2aWRxDJ+fxvsfKQ0t14yadMHx4UP3rcJ9 bH/g4uCnn9du63C1eRLgMNV7unBzjozxr7F3vxhXCqMCxoTnx/BZ2Yu8WR9cnH4c Zlbo++C1uRbD6DnL1amIFIT5FFCygQKh70izuEfwQDmiYO2f9jWxnPBy4E8G2mg7 NADurU+xmRRoaOuS9rzdhNiTe0ThWkJpo7nWMUj2wiKBprV8WTrIfrsnBHVEF9RV 6FyAOK9M0w1jg1M8DVJ1VNx0wiCSgHDa3GJ/1BT8x9J3p7RH8JdceUecpQc9Vzq7 o320FLdIq7Qt7kYRlZ/oKs7u3THrJ742kh0lL9f7GBWAbv8yCEirws8m5GpQKKM1 GrP6b2uKpScWnsAfYe8lFh7CCdMzRtRObnG56mWxQCdhC3Xyf+Y=
=2Qsg
-----END PGP SIGNATURE-----
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)