diff options
author | Vladimír Čunát <vcunat@gmail.com> | 2015-06-18 22:23:55 +0200 |
---|---|---|
committer | Vladimír Čunát <vcunat@gmail.com> | 2015-06-18 22:38:08 +0200 |
commit | 61596bf405de245c71630101869ea3f4e8f8a20a (patch) | |
tree | e712933bc34d25aba42b99907f879b5251585b29 /CONTRIBUTING.md | |
parent | 8e19ac8d7cc7018613ff51d9266dea81547df756 (diff) | |
parent | fe75f160324672d639469dc2da69f70d4eb466a4 (diff) | |
download | nixlib-61596bf405de245c71630101869ea3f4e8f8a20a.tar nixlib-61596bf405de245c71630101869ea3f4e8f8a20a.tar.gz nixlib-61596bf405de245c71630101869ea3f4e8f8a20a.tar.bz2 nixlib-61596bf405de245c71630101869ea3f4e8f8a20a.tar.lz nixlib-61596bf405de245c71630101869ea3f4e8f8a20a.tar.xz nixlib-61596bf405de245c71630101869ea3f4e8f8a20a.tar.zst nixlib-61596bf405de245c71630101869ea3f4e8f8a20a.zip |
Merge #8363: pure-darwin stdenv
Diffstat (limited to 'CONTRIBUTING.md')
-rw-r--r-- | CONTRIBUTING.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 519b2180b018..195d1ae6d0ac 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -44,7 +44,7 @@ * _If you don't want to install pkg in you profile_. * `nix-build -A pkg-attribute-name <path to your local nixpkgs folder>/default.nix` and check results in the folder `result`. It will appear in the same directory where you did `nix-build`. * If you did `nix-env -i pkg-name` you can do `nix-env -e pkg-name` to uninstall it from your system. - * nixos and it's modules + * nixos and its modules * You can add new module to you `nixos-configuration file` (usually it's `/etc/nixos/configuration.nix`. And do `sudo nixos-rebuild test -I nixpkgs=<path to your local nixpkgs folder> --fast` * If you have commits `pkg-name: oh, forgot to insert whitespace`: squash commits in this case. Use `git rebase -i`. @@ -56,7 +56,7 @@ * Create pull request. * Write the title in format `(pkg-name | service): improvement` * If you update the pkg, write versions `from -> to` - * Write in comment if you have tested your patch. Do not rely much on `TravisCL`. + * Write in comment if you have tested your patch. Do not rely much on `TravisCI`. * If you make an improvement, write why is it good. * Notify maintainers of the package. For example add to the message: `cc @jagajaga @domenkozar` |