Yeah, I'll have to dig through the gitlab docs to see how to do that. It's always kind of hard to find it.Hi Raymond,
On Thu, Jul 13, 2023 at 3:36 PM Raymond Toy <toy.raymond@gmail.com> wrote:
On 7/13/23 04:23, Erik Huelsmann wrote:
>
> cmucl-ticket
I guess this and other -ticket lists were created for Trac. I guess
gitlab doesn't automatically send emails from the issue tracker to any
mailing list? I've forgotten how this works, but I'd like to keep this
and have gitlab send issues to this mailing list.
The commit messages are being sent to an e-mail address (which can be a mailing list) due to project configuration. Maybe that's an option for issue updates too. Not sure.
Oops. I meant cmucl-imp, not cmucl-devel. The existing cmucl-help and cmucl-imp were created when cmucl moved to c-l.net, but we never actually moved the cons.org lists here.I'm also surprised that cmucl-devel and cmucl-help aren't here.
Neither of these exist on common-lisp.net, or at least, not if I have to go by https://mailman.common-lisp.net/listinfo. There *is* an archive for cmucl-help@common-lisp.net, but no trace of cmucl-devel@common-lisp.net (there is cmucl-imp@common-lisp.net, though).
> f2cl-ticket
>
> oct-cvs
> oct-ticket
>
I'd like to keep the above. I haven't worked too much on f2cl or oct in
a while, but they're not dead; they just work well enough for me now.
Mind if I migrate these to mailman3 now then? Once migrated, I won't be looking at them anymore and they're very low volume anyway, so migrating now won't interfere with on-going fierce discussions :-)
Go for it!
Again, thanks for updating the mailing lists.
Haha! It even uses cmucl as the example. I had forgotten about this page. :-)I
guess the burden is on me to have these projects send issue and git
emails to the right mailing list.
Yep. But it should be straight forward, at least for the commit mails. It's even documented in the site FAQ: https://common-lisp.net/faq/emailonpush