| Commit message (Expand) | Author | Age | Files | Lines |
|---|
| * | doc: fix examples | Yiyu Zhou | 2025-10-19 | 1 | -2/+2 |
| * | doc: update Nix code snippets format•••Command: `mdcr --config doc/tests/mdcr-config.toml doc/`
| Pol Dellaiera | 2025-04-17 | 1 | -3/+6 |
| * | Revert "treewide: replace `rev` with `tag`"•••This reverts commit 65a333600d5c88a98d674f637d092807cfc12253.
This wasn't tested for correctness with something like fodwatch [0],
and should not have been (self-)merged so quickly, especially without
further review.
It also resulted in the breakage of at least one package [1] (and that's
the one we know of and was caught).
A few packages that were updated in between this commit and this revert
were not reverted back to using `rev`, but other than that, this is a
1:1 revert.
[0]: https://codeberg.org/raphaelr/fodwatch
[1]: https://github.com/NixOS/nixpkgs/pull/396904 / 758551e4587d75882aebc21a04bee960418f8ce9
| Winter | 2025-04-08 | 1 | -2/+2 |
| * | treewide: replace `rev` with `tag` | Pol Dellaiera | 2025-04-07 | 1 | -2/+2 |
| * | treewide: Fix all Nix ASTs in all markdown files•••This allows for correct highlighting and maybe future automatic
formatting. The AST was verified to work with nixfmt only.
| Janne Heß | 2024-03-28 | 1 | -1/+5 |
| * | doc: use sri hash syntax•••The nixpkgs manual contains references to both sri hash and explicit
sha256 attributes. This is at best confusing to new users. Since the
final destination is exclusive use of sri hashes, see nixos/rfcs#131,
might as well push new users in that direction gently.
Notable exceptions to sri hash support are builtins.fetchTarball,
cataclysm-dda, coq, dockerTools.pullimage, elixir.override, and
fetchCrate. None, other than builtins.fetchTarball, are fundamentally
incompatible, but all currently accept explicit sha256 attributes as
input. Because adding backwards compatibility is out of scope for this
change, they have been left intact, but migration to sri format has been
made for any using old hash formats.
All hashes have been manually tested to be accurate, and updates were
only made for missing upstream artefacts or bugs.
| Colin Arnott | 2022-12-04 | 1 | -2/+2 |
| * | doc/crystal: Update to mention shard.lock file generation | Silvan Mosberger | 2021-10-30 | 1 | -2/+2 |
| * | doc: prepare for commonmark•••We are still using Pandoc’s Markdown parser, which differs from CommonMark spec slightly.
Notably:
- Line breaks in lists behave differently.
- Admonitions do not support the simpler syntax https://github.com/jgm/commonmark-hs/issues/75
- The auto_identifiers uses a different algorithm – I made the previous ones explicit.
- Languages (classes) of code blocks cannot contain whitespace so we have to use “pycon” alias instead of Python “console” as GitHub’s linguist
While at it, I also fixed the following issues:
- ShellSesssion was used
- Removed some pointless docbook tags.
| Jan Tojnar | 2021-06-07 | 1 | -1/+3 |
| * | doc: explicit Markdown anchors for top-level headings; remove metadata•••I used the existing anchors generated by Docbook, so the anchor part
should be a no-op. This could be useful depending on the
infrastructure we choose to use, and it is better to be explicit than
rely on Docbook's id generating algorithms.
I got rid of the metadata segments of the Markdown files, because they
are outdated, inaccurate, and could make people less willing to change
them without speaking with the author.
| Ryan Mulligan | 2021-01-01 | 1 | -1/+1 |
| * | crystal: use latest openssl | worldofpeace | 2020-02-28 | 1 | -1/+1 |
| * | docs: Add Crystal language framework section | Silvan Mosberger | 2019-08-26 | 1 | -0/+71 |
