And they’re all with different commit message:

“switched arse to bottom to create a more uplifting vibe”

“took arse out and put bottom in to keep my language warm and friendly”

“thought bottom would sound a lot nicer than arse, so I used it”

And so on…

TesseraC+

And who hasn’t contributed any code to this particular repo (according to github insights).

I see there an access violation…

Let’s be fair, it’s actually about all those people whose password is “password”. But it is annoying to those who use 15-character random strings for passwords.

That’s not very deep. Closer to plain old logistic regression, really.

Never tried magit, but it doesn’t matter. It couldn’t possibly be good enough to be worth using an inferior editor.

The ease with which I can only commit separate hunks with lazygit has ensured I use it for commits, too. And once I’ve opened it to do the commit, I may as well also press P.

Learning git is very easy. For example, to do it on Debain, one simply needs to run, sudo apt install lazygit

Not exactly. For example, you can’t make the whole thing, GPL snippet included, available under MIT. You can only license your own contribution however you want (in addition to GPL).

That seems a somewhat contrived example. Yes, it can theoretically happen - but in practice it would happen with a library, and most libraries are LGPL (or more permissive) anyway. By contrast, there have been plenty of stories lately of people who wrote MIT/BSD software, and then got upset when companies just took the code to add in their products, without offering much support in return.

Also, there’s a certain irony in saying what essentially amounts to, “Please license your code more permissively, because I want to license mine more restrictively”.