pcs3rd

If that's your intention, I would check to see if it's already a supported/testing device on PostmarketOS's wiki here. If not (and you already have some Linux experience), there's tooling maintained by the project that could help with porting. It doesn't look like there's an official lineage image for your device yet, so porting may be a bit more difficult. The better bet is probably with picking up something like a used lenovo 10e and installing PMOS, but I did find it slow when my 10e worked

Totally, slavery is still an issue everywhere, but this specifically is more of a case of a white person choosing for black people, and apparently it's making people uncomfortable AND could potentially be considered a breaking change. This is github dev's 'pros' list on twitter. https://twitter.com/Una/status/1271181775130279936?s=19 And to be honest, I don't think most black people here (in the US) think the word slave only applies to them, but that conversation doesn't belong here. Git itself seems to potentially have a better solution to this imaginary issue: just ask the user to name the head branch when running 'git init'. https://lore.kernel.org/git/20200609223624.GO6569@camp.crustytoothpaste.net/T/#mf6bab91e35ad94fe6ce272615219f887b9b8b440

For me it really isn't about the literal change in words. This matters more about the why github is doing it and the effects of them preforming said action. It is an unnecessary change that, in reality, is only being preformed because the bubbles in the boiling pot that America is started flowing over the brim. It doesn't effect or reduce police brutality, nor racism on the internet and on the streets. It doesn't change white on black or black on black violence, or actually any violence. The change isn't because it would only help developers (that use github) as a whole, but because it may bring good press, or press at all. And it has. Depending on implementation (if the default changes and 'master' aren't kept as an alias as mentioned by others), they break scripts. Lots of 'em. Please understand that this is my pov, and I hope this explains why I thought it was worth my time to put it over here. It may just be extremely poor timing on GitHub's part. I really do apologise if this comes through as an emotionally charged reply.

What would you suggest would be a more descriptive term? I feel that master describes it perfectly, since when a branch is first created, it is essentially a clone of the master branch, and the master branch is imo better described as a master copy.

That's because gitlab hasn't bothered yet.

A big factor behind this is about being politically correct @TofuHaroto . >Reasons 2&4.

Actually, that may be a humorous thing to hide away for april fool's...

If it were something like DNS, where it was changed to 'primary' and 'secondary', that makes sense. Changing 'master' and 'slave' terminologies on github doesn't make very much sense, considering that when a new branch is made, it is usually based off of the 'master' branch.

Even further, in this context, the terms 'master' and 'slave' are only being used to describe the flow of data and service types, similar to unix's 'parent' and 'child', not the status of a person or living thing.

Within the last few days, github has decided that the Terms 'master' and 'slave' with 'main' and so-on. The decision was odly made as a tweeted suggestion. There are currently arguments on twitter on wether or not that this is a distraction from black equality or a step forward. https://www.zdnet.com/article/github-to-replace-master-with-alternative-term-to-avoid-slavery-references/ Personally, I think this is dumb and it will break everyone's automation scripts.

@Nayr348 what about jackd?