| Commit message (Collapse) | Author | Age |
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
There was just no way to actually use this script in a useful manner.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
These should be generated by `reuse`
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
`cargo upgrade` raises the update boundaries in `Cargo.toml`, whilst
`cargo update` just fetches the newest version (that conform to the
boundaries) for `Cargo.lock`.
|
|
|
|
|
| |
This results in a reasonable name for the resulting PDF, instead of the
generic `main.pdf`.
|
|
|
|
|
|
| |
Every symlink in the `./templates` directory is now replaced with
the file it points to, making it obvious that this file should not be
edited.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Symlinks are copied verbatim, when nix initializes a template, thus
symlinking common files does not work.
|
|
|
|
|
| |
Otherwise, the `update_common_files` script will try to instantiate
files in there, which is just useless noise.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|