| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
| |
The convention is to use `pkgs` or `packages` for overlays and
definition of custom packages. Since I'm already using `pkg` for go,
I prefer to use `packages` for my scripts.
|
| | |
|
| |
|
|
|
|
|
| |
For the python tools, we need the python runtime to be available. For
this we need to specify the dependencies in `propagatedBuildInputs`.
The same is true for flamegraph and perf.
|
| | |
|
| |
|
|
|
|
| |
The tool can calculate some stats about authors in a git repository. It
computes the number of lines that are authored by authors at a given
revision (HEAD by default), and the number of commits.
|
| |
|
|
|
|
|
|
|
|
|
| |
In the `mkSystem` function, instead of defining each tools, let's import
all of them at once. This works both with installing a tool from a
module or running them from the CLI.
Change-Id: Ia44ff9a45b54a1ecea6f6b02b4cad2956799f627
Reviewed-on: https://cl.fcuny.net/c/world/+/682
Tested-by: CI
Reviewed-by: Franck Cuny <franck@fcuny.net>
|
|
|
Running this command in a repository will report how many lines in the
current paths were created by different author, for a given revision. If
no revision is specific, HEAD is assumed.
Change-Id: I3fbed4f35a05e12fef22a72d7231727c05c50c96
Reviewed-on: https://cl.fcuny.net/c/world/+/445
Tested-by: CI
Reviewed-by: Franck Cuny <franck@fcuny.net>
|
