It obviously depends on your exact git workflow, but my last team had things setup so that the code content of a MR was automatically squashed on merge, and the text if the MR itself was automatically set as the content of the new singular git commit.

This was largely the best of both worlds because your commits could have almost any text, and the description of what changed could be updated as needed when making the MR. But it ultimately ended up in the git history where it belonged.

Of course, I still had some trouble trying to get the team to describe their changes well in the MR at times - but that’s a different problem entirely.

It wasn’t always an option - around the time of the first big mass migration of Reddit users it wasn’t something you could do. I actually wrote a tool at that time that could automate the manual action of re-subscribing / re-blocking everything.

But yeah, these days it’s a feature of Lemmy itself, which is great because it’s much more efficient than trying to do things client-side.

Super cool project. FYI it does require converting your ebooks to a special format.

I suspected as much since it’s using an Arduino Mega - very battery efficient I’m sure, but very underpowered.

Found a blog post that gives a quick overview of how to do git via email in general: https://peter.eisentraut.org/blog/2023/05/09/how-to-submit-a-patch-by-email-2023-edition

So at least from my understanding you’d make your changes, email the contents of the patch to the maintainer, and then they’d apply it on their side, do code review, email you comments, etc. until it was in an acceptable state.

There’s also the full kernel development wiki that goes into all the specifics: https://www.kernel.org/doc/html/v4.16/process/howto.html

(I never got through the whole thing)

I’ll also throw out: aging infrastructure, build systems, coding practices, etc.

I looked into contributing to the kernel - it’s already an uphill battle to understand such a large, complex piece of software written almost entirely in C - but then you also need to subscribe to busy mailing lists and contribute code via email, something I’ve never done at 30 and I’m betting most of the younger generation doesn’t even know is possible. I know it “works” but I’m really doubting it’s the most efficient way to be doing things in 2024 - there’s a reason so many infrastructure tools have been developed over the years.

The barriers to entry for a lot of projects is way too high, and IMO a lot of existing “grey” maintainers, somewhat understandably, have no interest in changing their processes after so much time. But if you make it too hard to contribute, no one will bother.

I’m surprised by Helldiver’s. Has there been some performance patches? I tried playing that on my deck near launch and it really struggled even at minimum settings - I can’t imagine how it would run at higher difficulties.

I would kindly redirect any kind comments you have, or suggests for items to add, to @[email protected], the original creator of the list.

I am but a humble cross-poster.