diff options
| author | aszlig <aszlig@redmoonstudios.org> | 2016-05-06 21:32:21 +0200 |
|---|---|---|
| committer | aszlig <aszlig@redmoonstudios.org> | 2016-05-06 21:32:21 +0200 |
| commit | 64ca91cac9b5dd520a736528a3f0a29ba1480593 (patch) | |
| tree | 00ab280ed6421ff937df98ac10e7c2061f50c5e1 /nixos/tests/boot-stage1.nix | |
| parent | eb6e366446ea00d92e2a39d2700dc4faa0a6bdf0 (diff) | |
nixos/tests/boot-stage1: Add myself to maintainers
As @edolstra pointed out that the kernel module might be painful to
maintain. I strongly disagree because it's only a small module and it's
good to have such a canary in the tests no matter how the bootup process
looks like, so I'm going the masochistic route and try to maintain it.
If it *really* becomes too much maintenance burden, we can still drop or
disable kcanary.
Signed-off-by: aszlig <aszlig@redmoonstudios.org>
Diffstat (limited to 'nixos/tests/boot-stage1.nix')
| -rw-r--r-- | nixos/tests/boot-stage1.nix | 6 |
1 files changed, 4 insertions, 2 deletions
diff --git a/nixos/tests/boot-stage1.nix b/nixos/tests/boot-stage1.nix index 311acd7bb1c4..ad253d23c543 100644 --- a/nixos/tests/boot-stage1.nix +++ b/nixos/tests/boot-stage1.nix @@ -1,4 +1,4 @@ -import ./make-test.nix { +import ./make-test.nix ({ pkgs, ... }: { name = "boot-stage1"; machine = { config, pkgs, lib, ... }: { @@ -150,4 +150,6 @@ import ./make-test.nix { $machine->succeed('pgrep -a -f \'^@canary3$\'''); $machine->succeed('pgrep -a -f \'^kcanary$\'''); ''; -} + + meta.maintainers = with pkgs.stdenv.lib.maintainers; [ aszlig ]; +}) |