Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

swayidle: 1.1 -> 1.2 #55513

Closed
wants to merge 1 commit into from
Closed

swayidle: 1.1 -> 1.2 #55513

wants to merge 1 commit into from

Conversation

FlorianFranzen
Copy link
Contributor

Motivation for this change

Update swayidle to latest release.

Maintainer is @primeos

Things done
  • Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
  • Built on platform(s)
    • NixOS
    • macOS
    • other Linux distributions
  • Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
  • Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
  • Tested execution of all binary files (usually in ./result/bin/)
  • Determined the impact on package closure size (by running nix path-info -S before and after)
  • Assured whether relevant documentation is up to date
  • Fits CONTRIBUTING.md.

@FlorianFranzen
Copy link
Contributor Author

@primeos: Sorry, just saw I am five days late to the party. Not sure why GitHub did not show me a merge conflict. Guess you can not rely on that.

@FlorianFranzen FlorianFranzen deleted the swayidle branch February 10, 2019 12:16
@primeos
Copy link
Member

primeos commented Feb 10, 2019

@FlorianFranzen No problem and yes, this is a bit unfortunate (would be great if GitHub would complain if the merge is effectively a no-op).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
10.rebuild-darwin: 0 10.rebuild-linux: 0
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
3 participants
@FlorianFranzen @primeos @GrahamcOfBorg