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 105
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: 3cff2fbc0a37
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: 589d270ce440
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
- 3 commits
- 2 files changed
- 3 contributors
Commits on Oct 12, 2018
-
Hard-code kubernetes version as the upstream python script is broken/not-up-to-date Signed-off-by: Vincent Demeester <vincent@sbr.pm> (cherry picked from commit ba98a7a) Backport of #47765
Configuration menu - View commit details
-
Copy full SHA for c0c5ea1 - Browse repository at this point
Copy the full SHA c0c5ea1View commit details -
minikube: bump version 0.29.0 -> 0.30.0
This is a fix release for CVE-2018-1002103. More details in kubernetes/minikube#3208 (cherry picked from commit e5ee89f) Backport of #48256
Configuration menu - View commit details
-
Copy full SHA for c0c867d - Browse repository at this point
Copy the full SHA c0c867dView commit details -
nixos/network-interfaces-scripted: fix container networking bug
When a bridge interface was reconfigured, running containers using this bridge lost connectivity: restarting network-addresses-brN.service triggered a restart of network-setup.service via a "partOf" relationship introduced in 07e0c0e. This in turn restarted brN-netdev.service. The bridge was thus destroyed and recreated with the same name but a new interface id, causing attached veth interfaces to lose their connection. This change removes the "partOf" relationship between network-setup.service and network-addresses-brN.service for all bridges. (cherry picked from commit 2742063)
Configuration menu - View commit details
-
Copy full SHA for 589d270 - Browse repository at this point
Copy the full SHA 589d270View commit details
There are no files selected for viewing