What’s wrong with having a some year old software? Does it do what you need? Yes. Then what? I have all I need on Debian. Why should I care of new updates. Security? Yes we have Debian security because of that. Look, y’all had the xyz backdoor package in your systems because it was new. Me as a Debian stable user I didn’t have to deal with it. Did I lose something by not having the latests software? No. Well maybe less crashes.

Most privative software also gets weekly updates. Does it make it better? No. You may prefer that.

Also I don’t get the point about the version numbering of Debian packages. Every team uses the versioning they want.

From my experience software that updates a lot tends to break old features a lot too.

Debian suporting freesoftware projects or other stuff doesn’t look as a relevant argument. I mean if you prefer using privative stuff and using that kind of software. Do whatever you like with your Google/Facebook/Apple friends.

But don’t come intoxicate the community with this bullshit.

You can always adapt to your how repo. But yeah, that’s the point. If you can trust people to make changes on a repo then you should be able to trust them in using some kind of commit structure.

Generic names are probably used in order to crate a familiar, easy to remember, structurized commit format.

You can always water it down. The point is to have some order in the commits. Otherwise is just messy.

Please use Conventional Commits. Simple and easy to use. Plus it is very easy so combine with Versioning techniques like Semantic Versioning.

You can create aliases

This is the way

Nice, my lovely C syntax. Thank you!

I thought major software devs used signed commits. I don’t have that much git experience and I have everything gpg signed even since the first repo I did.

This makes me question a lot of software.

How? For real I hate python not having ; and { and depending on tabs and spaces (PAIN)

Holy shit people are toxic. The poor guy that responded.

o7 the real chad. I hope others maintain his legacy inside AMD.

You can use backports too!

The disease part is too real

I did that my self (fixed the chip), the cables and everything shiped with it are trash.

If you want to install this please DO NOT USE THE CH341A programmer. That fucking shit has the internal control signals and data signals at 5V and the bios chips usually work at 3.3V or lower.

The CH341A is defective by design and the Chinese manufacturers don’t care. There are fixes online, but still the chip works badly.

If you want to install libreboot, please use any other option given at Libreboot docs. I lost too many hours because of the fucking Chinese ch341a. Which I solved quickly with a pi pico board.

In any case do not use this guy’s video as an example. The instructions of the video ARE WRONG and you may fry your bios. Don’t be fooled by this youtuber confidence. Follow the docs.

I’ve installed it on a x220.

Pretty much sums up every thing

Well how fucked up are his/her commits? Straight blinding matterial + useless?

I get is more liberal which I understand why. But that means that changes to the software do not need to be shared. Which for normal users it really does not matter. But again we are giving to multi corporations so much in exchange of nothing. When again they don’t treat their users the same way.

MIT is a good licence as an idea. In reality, multi corporations are evil AF. The idea of free software in a sense is that free software can get so much better than privative one, eventually forcing privative companies to implement it them self on their programs.

If giving and taking was 1:1 in software community then again, MIT license is perfect. In reality it isn’t. For major programs that have a lot of implication on new programs I do not recommend MIT and similar. For feature like projects is totally okay IMO.

Yeah Musl is pretty good to learn C libs but the main red flag is the MIT Licence

glibc is great, but holy shit the source code is obscured into oblivion, so hard to understand, with hardcoded optimizations, and compiler optimizations. I understand how difficult is to find vulnerabilities. A bit sad that the only C lib truely free software is so hard to actually read its code or even contribute to it.