From 2badac1a4a24b66eb56d0e449a3f58d3f8605285 Mon Sep 17 00:00:00 2001 From: "http://joeyh.name/" Date: Sun, 12 Oct 2014 20:14:36 +0000 Subject: Added a comment --- .../comment_3_a07abdd1dc21a69ad6be0526edaeffc1._comment | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 doc/forum/Git_annex_hangs/comment_3_a07abdd1dc21a69ad6be0526edaeffc1._comment (limited to 'doc') diff --git a/doc/forum/Git_annex_hangs/comment_3_a07abdd1dc21a69ad6be0526edaeffc1._comment b/doc/forum/Git_annex_hangs/comment_3_a07abdd1dc21a69ad6be0526edaeffc1._comment new file mode 100644 index 000000000..452f175a5 --- /dev/null +++ b/doc/forum/Git_annex_hangs/comment_3_a07abdd1dc21a69ad6be0526edaeffc1._comment @@ -0,0 +1,13 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="209.250.56.54" + subject="comment 3" + date="2014-10-12T20:14:36Z" + content=""" +Probably the same problem reported here: + + +I guess this is a mismatch between the version of git that git-annex was built with and the version it's using. In particular, git check-attr behavior varies between git older than 1.7.7 and newer, and git-annex picks the version at build time. + +So, I think this is a broken Ubuntu PPA, and if that's the current one, the maintainer of the PPA needs to be contacted to update the git-annex to match the git version, or depend on an appropriate git version. +"""]] -- cgit v1.2.3 From 9537e5efb88d9f8e92cf269f1ca2e2783c98ba57 Mon Sep 17 00:00:00 2001 From: ghen1 Date: Sun, 12 Oct 2014 21:03:01 +0000 Subject: Added a comment --- .../comment_2_8ca9156d21d9f3db0d83d6aa9b69caa0._comment | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) create mode 100644 doc/forum/git-annex_vicfg_preferred_content_settings_are_not_being_saved/comment_2_8ca9156d21d9f3db0d83d6aa9b69caa0._comment (limited to 'doc') diff --git a/doc/forum/git-annex_vicfg_preferred_content_settings_are_not_being_saved/comment_2_8ca9156d21d9f3db0d83d6aa9b69caa0._comment b/doc/forum/git-annex_vicfg_preferred_content_settings_are_not_being_saved/comment_2_8ca9156d21d9f3db0d83d6aa9b69caa0._comment new file mode 100644 index 000000000..467d45740 --- /dev/null +++ b/doc/forum/git-annex_vicfg_preferred_content_settings_are_not_being_saved/comment_2_8ca9156d21d9f3db0d83d6aa9b69caa0._comment @@ -0,0 +1,17 @@ +[[!comment format=mdwn + username="ghen1" + ip="66.41.70.34" + subject="comment 2" + date="2014-10-12T21:03:01Z" + content=""" +The custom settings I had made before (the rest are still commented out): +trust a8372263-6eba-47e2-9604-3e2c9bbb6d42 = trusted +wanted 3e2bcb1e-39ad-4863-a9ce-a18a262644c1 = present or (not include=/Books/*) +wanted a8372263-6eba-47e2-9604-3e2c9bbb6d42 = present or include=/Books/* + +I am trying to comment them out again. + +Based on your answer, I guessed that these settings don't just reset to default when they are commented out, so I tried changing the above trusted setting to semitrusted, and sure enough it worked. + +So it seems once these settings are made they can't be commented out again, and any invalid settings are ignored? +"""]] -- cgit v1.2.3