Added a comment
authorlhunath@3b4ff15f4600f3276d1776a490b734fca0f5c245 <lhunath@web>
Tue, 3 Mar 2020 20:33:47 +0000 (20:33 +0000)
committeradmin <admin@branchable.com>
Tue, 3 Mar 2020 20:33:47 +0000 (20:33 +0000)
doc/bugs/git-annex_upgrade_fails/comment_5_ae191f06cc858bef86dc79d44f0aedba._comment [new file with mode: 0644]

diff --git a/doc/bugs/git-annex_upgrade_fails/comment_5_ae191f06cc858bef86dc79d44f0aedba._comment b/doc/bugs/git-annex_upgrade_fails/comment_5_ae191f06cc858bef86dc79d44f0aedba._comment
new file mode 100644 (file)
index 0000000..876cf07
--- /dev/null
@@ -0,0 +1,11 @@
+[[!comment format=mdwn
+ username="lhunath@3b4ff15f4600f3276d1776a490b734fca0f5c245"
+ nickname="lhunath"
+ avatar="http://cdn.libravatar.org/avatar/6388e539b56b3875cc9aceb9f404b3ad"
+ subject="comment 5"
+ date="2020-03-03T20:33:47Z"
+ content="""
+Seems like git-annex should report on that.  Simply saying \"git-annex: upgrade: 1 failed\" because git is 2.21 is extremely unhelpful.  If git-annex requires a certain version of git, it should test for that and be explicit about that requirement in its error output.  I needed this comment in order to resolve the issue.
+
+For me, 2.21 is just what macOS ships with.
+"""]]