This repository was archived by the owner on Apr 12, 2021. It is now read-only.
-
-
Notifications
You must be signed in to change notification settings - Fork 104
Permalink
Choose a base ref
{{ refName }}
default
Choose a head ref
{{ refName }}
default
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
base repository: NixOS/nixpkgs-channels
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: 127634e4af81
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
...
head repository: NixOS/nixpkgs-channels
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: 52cc1800d41e
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
- 9 commits
- 12 files changed
- 7 contributors
Commits on Jul 7, 2020
-
Configuration menu - View commit details
-
Copy full SHA for a844cd8 - Browse repository at this point
Copy the full SHA a844cd8View commit details
Commits on Jul 17, 2020
-
maintainers-list: add a GDPR note, avoid unnecessary data collection
This change was preceded by the idea of adding a pronoun field to the file, which we determined to be a bad idea: * maintainers-list: add pronoun to the optional fields I often do not know how to address maintainers, so giving them the ability to specify their pronouns is helpful for communication purposes. * maintainers-list: add pronoun for Profpatsch maintainers-list: make the pronoun field into a list Some people have a set of pronouns they are fine with, so let’s make that possible. Based on feedback by somebody With An Idea™ of the topic. * maintainers-list: remove the pronouns field The discussion around the field raised a good point, quoting: > What you are proposing here is keeping an irrevocable permanent > history of people’s pronouns. It makes anybody would want to do bad > things with it one small script away from a list of which Nixpkgs > contributors are trans. Even looking at the history of name > changes (which we probably also shouldn’t store) wouldn’t be nearly > as reliable a source. While it might be tempting to say that > participating in this would be optional, it would be establishing a > de facto standard location for this information, that might make > people feel compelled to participate or accept having the wrong > pronoun used. Compounding this is the fact that the people who will > be most comfortable using this field are the people who have never > changed their pronouns. If they decide to in future, they now have > to choose between permanently marking themselves as somebody who > changed or deleted their pronouns (which is dangerous) or leaving > the wrong pronouns up. Because of this, I think that over time this > list would probably result in even more people being referred to by > the wrong pronouns, because of outdated entries that are dangerous > to correct. > > **This idea is extremely dangerous**. If somebody wants to publish > their pronouns, they can already do that on their website or GitHub > profile, without having to include that information in a large > public dataset with history tracking. So let’s remove it again.
Configuration menu - View commit details
-
Copy full SHA for f13283c - Browse repository at this point
Copy the full SHA f13283cView commit details
Commits on Jul 20, 2020
-
Configuration menu - View commit details
-
Copy full SHA for 85091e0 - Browse repository at this point
Copy the full SHA 85091e0View commit details -
Configuration menu - View commit details
-
Copy full SHA for 1af8759 - Browse repository at this point
Copy the full SHA 1af8759View commit details -
Configuration menu - View commit details
-
Copy full SHA for 3dc3f01 - Browse repository at this point
Copy the full SHA 3dc3f01View commit details
Commits on Jul 21, 2020
-
Merge pull request #93343 from Profpatsch/maintainers-pronoun-field
maintainers-list: add a GDPR note, avoid unnecessary data collection
Configuration menu - View commit details
-
Copy full SHA for 8316e0c - Browse repository at this point
Copy the full SHA 8316e0cView commit details -
Merge pull request #72320 from sweber83/sw-zigbee2mqtt
zigbee2mqtt package & module
Configuration menu - View commit details
-
Copy full SHA for 72f66e7 - Browse repository at this point
Copy the full SHA 72f66e7View commit details -
Configuration menu - View commit details
-
Copy full SHA for facca97 - Browse repository at this point
Copy the full SHA facca97View commit details -
Merge pull request #93572 from marsam/update-minisign
minisign: 0.8 -> 0.9
Configuration menu - View commit details
-
Copy full SHA for 52cc180 - Browse repository at this point
Copy the full SHA 52cc180View commit details
Loading
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff 127634e4af81...52cc1800d41e