From: Joey Hess <joeyh@joeyh.name>
Date: Mon, 2 May 2022 18:24:32 +0000 (-0400)
Subject: comment
X-Git-Tag: archive/raspbian/10.20250416-2+rpi1~1^2~75^2~11
X-Git-Url: https://dgit.raspbian.org/?a=commitdiff_plain;h=1c00731f9ed2ff088cd2ccce9745c3119b68af5c;p=git-annex.git

comment
---

diff --git a/doc/todo/nitpick__58___show_one_column_per_UUID_in_git_annex_lis/comment_1_e6d9efa01ddeb129469b3b8a4205cb3f._comment b/doc/todo/nitpick__58___show_one_column_per_UUID_in_git_annex_lis/comment_1_e6d9efa01ddeb129469b3b8a4205cb3f._comment
new file mode 100644
index 0000000000..dec51638b8
--- /dev/null
+++ b/doc/todo/nitpick__58___show_one_column_per_UUID_in_git_annex_lis/comment_1_e6d9efa01ddeb129469b3b8a4205cb3f._comment
@@ -0,0 +1,16 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 1"""
+ date="2022-05-02T18:22:37Z"
+ content="""
+I think you would be better off using `git-annex whereis` in 
+this kind of situation.
+
+--unique-repos would be a fix specific to your own situation of having
+multiple names for a repo, but it would not help a user who had similar
+difficulty reading the output just because they have a lot of different
+repos. 
+
+The output of `git-annex whereis` is better suited to scaling to a lot of
+repos.
+"""]]