From 51e6294d1556b39610038f36a5cf6c6fc6091052 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Tue, 20 Dec 2022 14:30:18 -0400 Subject: [PATCH] comment --- ..._3d8dcde00f8df7961490ef81f5400824._comment | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) create mode 100644 doc/git-annex-benchmark/comment_2_3d8dcde00f8df7961490ef81f5400824._comment diff --git a/doc/git-annex-benchmark/comment_2_3d8dcde00f8df7961490ef81f5400824._comment b/doc/git-annex-benchmark/comment_2_3d8dcde00f8df7961490ef81f5400824._comment new file mode 100644 index 0000000000..ae2cccf2e3 --- /dev/null +++ b/doc/git-annex-benchmark/comment_2_3d8dcde00f8df7961490ef81f5400824._comment @@ -0,0 +1,19 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 2""" + date="2022-12-20T18:20:01Z" + content=""" +That --list turns out to come from the criterion library, and you can +actually use it but only if you provide the mandatory "-- command" +parameters too. For example: + + git-annex benchmark --list -- version + version + +That's not useful at all, since all if can list is the same benchmark you +provide on input. But this is a consequence of supporting other criterion +options like --iters and --csv that can be useful. + +`git-annex benchmark` does not use a canned set of benchmarks; it +benchmarks a git-annex subcommand or subcommands that you specify. +"""]]