News for hackers. Stuff that matters.
Re:Email and Git = <3 by catern on Thursday October 12, 2023 @08:50AM (#37856466)
You don't have to subscribe to send a patch to a mailing list.
Re:Email and Git = <3 by oefrha on Thursday October 12, 2023 @09:01AM (#37856587)
I have more than once subscribed just to report a bug or send a patch because the mailing list rejects emails from non-subscribers.

Edit: Btw, yes I have done the periodically-check-archive thing in the past, thank you. Hated it. Also missed a response once because I forgot to check and replier didn't CC. I realized like a month later.

Re:Email and Git = <3 by Hackbraten on Thursday October 12, 2023 @09:07AM (#37856652)
Even then, you’re free to opt into daily digests if you’re a subscriber. The message ID allows you to reply to individual messages and threads nonetheless.
Re:Email and Git = <3 by catern on Thursday October 12, 2023 @11:24AM (#37858522)
It is unfortunate that there are poorly-managed projects with poorly-managed mailing lists (just like there are poorly-managed projects on Github), but sourcehut at least requires a properly-managed mailing list, and I think you should evaluate this workflow on that standard. Tell poorly-managed projects to move to sourcehut, if you want to fix this issue.
Re:Email and Git = <3 by sjamaan on Thursday October 12, 2023 @08:59AM (#37856571)
Presumably you'd be interested in any feedback, and not everyone CCs the original author in their reply.
Re:Email and Git = <3 by nolist_policy on Thursday October 12, 2023 @10:56AM (#37858093)
Reply-to-all is the standard policy on most mailing lists. Especially on -devel lists since you'll pull in (CC:) people outside of the mailing list (cross-project) into discussions from time to time.
Re:Email and Git = <3 by Avamander on Thursday October 12, 2023 @10:59AM (#37858137)
I know more than one occasion where that has gotten an angry reply.

It's also not the default in many clients. It's tedious and error-prone.