| Commit message (Collapse) | Author | Age |
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
This re-introduces the old stable ZFS version we had in the past following
the many predicted issues of ZFS 2.2.x series, that is much more stable
than any further ZFS version at the moment.
I am also removing myself from maintenance of any further ZFS versions as I am
planning to quit ZFS maintenance at some point.
In the meantime, for users like me who depend on ZFS for critical operations, here is a ZFS version
that is known to work for LTS kernels.
|
|
|
|
| |
Was removed in https://github.com/NixOS/nixpkgs/pull/268407
|
| |
|
|
|
|
| |
Updated to reflect reality: Eelco is not acting as a code owner of these files
|
| |
|
| |
|
| |
|
|
|
|
| |
The in-tree version has been broken for a while, so now is probably a good time to rip off the band-aid.
|
|\
| |
| | |
Emscripten docs: reword and remove mention of `nix-env`
|
| |
| |
| |
| | |
also notify on documentation changes
|
| | |
|
|/ |
|
|\ |
|
| |
| |
| |
| |
| | |
matthewbauer has been missing for almost a year now, it does not seem reasonable
to keep them and spam their GitHub notifications further.
|
| | |
|
|\ \
| | |
| | |
| | |
| | | |
nixos/forgejo: fork from nixos/gitea (split)
close https://github.com/NixOS/nixpkgs/issues/244866
|
| | | |
|
| | | |
|
|\ \ \
| | | |
| | | | |
[RFC 140] Simple package paths, part 1b: Enabling the directory structure
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This introduces the `pkgs/by-name` directory as proposed by RFC 140.
Included are:
- The implementation to add packages defined in that directory to the
top-level package scope
- Contributer documentation on how to add packages to it
- A GitHub Actions workflow to check the structure of it on all PRs
|
|\ \ \ \
| |/ / /
|/| | | |
File set combinators base: `lib.fileset.toSource`
|
| | | | |
|
|\ \ \ \
| |_|_|/
|/| | | |
[RFC 140] Simple package paths, part 1a: Checking tool
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Adds an internal CLI tool to verify Nixpkgs to conform to RFC 140.
See pkgs/test/nixpkgs-check-by-name/README.md for more information.
|
|/ / / |
|
|\ \ \
| | | |
| | | | |
Clean up contributing documentation
|
| |/ / |
|
|/ / |
|
| |
| |
| |
| | |
Forgot about that in https://github.com/NixOS/nixpkgs/pull/248166
|
| |
| |
| |
| | |
Was removed in f397309f4e6c7a219a7703b629f6a4e8d4e7a58b
|
| |
| |
| |
| |
| |
| |
| | |
I want to take ownership of this part of the documentation, especially
with the cleanup in https://github.com/NixOS/nixpkgs/pull/245243. Doing so
before that PR is merged also allows me to get notified about any potential
future merge conflicts before they happen.
|
| | |
|
|/ |
|
| |
|
|
|
|
|
|
|
|
|
| |
It is hard to get people to test changes to our kernel expression on
anything other than x86_64 and aarch64 before merging changes.
Therefore, I would like to be notified of PRs opened agains this
file, so that I can hopefully catch breakage before it is merged,
rather than afterwards.
|
|
|
|
| |
So I can see changes on NGINX.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I don't claim ownership of anything, but I would like to be notified
of PRs opened against the following paths where I've put a lot of
work into cleanup and deduplication:
lib/systems
pkgs/stdenv
pkgs/build-support/cc-wrapper
pkgs/development/compilers/gcc
Apparently CODEOWNERS is how you tell github you want to be notified
of such things.
|
| |
|
|
|
|
|
| |
This is long overdue, Lily has done more than me for Node.js in Nixpkgs
by this point.
|
| |
|
| |
|
|
|
|
| |
This will make my work easier about knowing what is going on with ZFS.
|
| |
|
|\
| |
| | |
nixos/qemu-vm: refactor bootDisk using make-disk-image
|
| |
| |
| |
| |
| |
| | |
I do a lot of work on QEMU VM and make-disk-image and I was bitten by an
unnotified change recently, so I want to chime in the future changes of
this file.
|
|\ \
| |/
|/| |
CODEOWNERS: add RaitoBezarius to llvm tree
|
| | |
|
|/ |
|
| |
|