vim
/
tpfan
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Update note on GitHub's renaming

dev
Michael De Roover 2020-09-09 13:48:37 +02:00
parent 1697a6c6c5
commit dde1f1454c
Signed by: vim
GPG Key ID: 075496E232CE04CB
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
README.md
View File

@ -15,9 +15,9 @@ It appears that this fan controller might work on other ThinkPads too. See if yo
#### Why is this repo's "main" branch called nigger?
With all the changes [GitHub](https://www.cnet.com/news/microsofts-github-is-removing-coding-terms-like-master-and-slave) and ISC as well (for [BIND](https://gitlab.isc.org/isc-projects/bind9) anyway, [ISC dhcp](https://gitlab.isc.org/isc-projects/dhcp) and [Kea](https://gitlab.isc.org/isc-projects/kea) are somehow unchanged) are pushing, and now even [RFC8499](https://tools.ietf.org/html/rfc8499) changing DNS terminology to "primary" and "secondary" servers (but still leaving references to master elsewhere, because why do these things properly), I felt a strong need to not call my main branch the heavily loaded term "master". You know, it's so offensive. So I figured that I had to choose something less offensive. Nigger sounded just right. It's about as effective as changing a name to main too.
You can rename your local branch if you desire. Unless you're a developer on the project it won't cause any issues, certainly not on the level that renaming `master` which just like `origin` is engrained *everywhere* within Git does. Or you can checkout to `dev` and get the latest features. I generally don't push changes unless I've tested them on my own x220 anyway. Should be stable enough.
You can checkout to master if you desire. Or you can checkout to `dev` and get the latest features. I generally don't push changes unless I've tested them on my own x220 anyway. Should be stable enough.
Note on GitHub's change to main - this appears to have been false news. A few weeks after the news broke on this, I tried to make a new repo for testing on GitHub. The default branch name even for that new repo was "master". When the news broke there was uncertainty whether the change would apply to all repos including existing ones (which would break all repositories to an extent barely imaginable), or whether it would only apply to new ones. It seems that it applied to neither. Makes you wonder who spread that news, and what the reason for it could've been.. one might imagine it to be a good way to add credibility to demands towards other organizations to also change their master branch name. After all, GitHub is pretty huge. If they can do it, why not your organization? But that's just speculation on my end. That said, GitHub appears to have never actually made that change. As such this repository now has a master branch once again as well.
Apparently GitHub will change to main at the first of October. See [github/renaming](https://github.com/github/renaming) for more details. Can't wait to see the mayhem!
#### Disclaimer
Generally speaking the fan control only becomes more fine-grained with this script and shouldn't damage your laptop. However please ensure that you clean your fan and change the thermal grease often, twice a year or so. That will do the most by far to reduce fan speeds and temperature. And by manually controlling the fan, it goes without saying that there is no warranty anymore. You do this at your own risk.