diff options
| author | Adam Joseph <adam@westernsemico.com> | 2022-08-21 15:23:54 -0700 |
|---|---|---|
| committer | Rick van Schijndel <Mindavi@users.noreply.github.com> | 2022-10-19 20:22:45 +0200 |
| commit | 2df2b52806129828a1dafaa093027f10817e5b3b (patch) | |
| tree | c003b2a698e4d9ef258f201a088082d696194fa3 /pkgs/development/python-modules/rangehttpserver | |
| parent | ac92b409b36f75fc2772c3333346174cb42d5352 (diff) | |
boost/generic.nix: reference commit-hash in comment
The explanation for the conditional introduced by
61d9f201baeef4c4bb91ad8a8f5f89b747e0dfe4 is longer than a reasonable
inline comment should be. It directed the reader to use `git blame`,
but that tends to bitrot. Let's point the user to a specific nixpkgs
git hash.
This commit cannot be squashed into the previous commit, because a
commit cannot mention its own commit-hash (without performaing an
expensive double-sha1 preimage attack, of course).
Diffstat (limited to 'pkgs/development/python-modules/rangehttpserver')
0 files changed, 0 insertions, 0 deletions