From 8b55b33e47d4b582d482706fced8dee0c6a37c05 Mon Sep 17 00:00:00 2001 From: "http://joeyh.name/" Date: Wed, 4 Jun 2014 18:04:31 +0000 Subject: Added a comment --- .../comment_1_ff53fa0b5f0c4a6554a37e3309e26925._comment | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 doc/forum/views___40__branches__41___never_get_deleted/comment_1_ff53fa0b5f0c4a6554a37e3309e26925._comment diff --git a/doc/forum/views___40__branches__41___never_get_deleted/comment_1_ff53fa0b5f0c4a6554a37e3309e26925._comment b/doc/forum/views___40__branches__41___never_get_deleted/comment_1_ff53fa0b5f0c4a6554a37e3309e26925._comment new file mode 100644 index 000000000..61fcbfeb4 --- /dev/null +++ b/doc/forum/views___40__branches__41___never_get_deleted/comment_1_ff53fa0b5f0c4a6554a37e3309e26925._comment @@ -0,0 +1,12 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="108.236.230.124" + subject="comment 1" + date="2014-06-04T18:04:30Z" + content=""" +You can delete the view branches if you like. I have considered making moving views clean up old branches, but I have also considered reusing existing view branches when popping back to an old view. + +git-annex unused can't look at branches that aren't there. Perhaps you have pushed the view branches to a remote repository, and it's checking those branches of the remote? See git branch -a. + +I think that it makes sense for unused to ignore (local) view branches, since these are by definition supposed to be views of an existing branch, so looking at the branch should be sufficient (and if the view is out of date and has files that have since been deleted from the branch, the user's intent is not to preserve those from unused reaping). So, made that change. +"""]] -- cgit v1.2.3 From 22f444521a9c5e2c291822d9fd8abd772ba67c83 Mon Sep 17 00:00:00 2001 From: "http://joeyh.name/" Date: Wed, 4 Jun 2014 18:07:11 +0000 Subject: Added a comment --- .../comment_1_f30b69c11b487334ef02ce7bfcdeb36c._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/bugs/SanityCheckerStartup_crashed/comment_1_f30b69c11b487334ef02ce7bfcdeb36c._comment diff --git a/doc/bugs/SanityCheckerStartup_crashed/comment_1_f30b69c11b487334ef02ce7bfcdeb36c._comment b/doc/bugs/SanityCheckerStartup_crashed/comment_1_f30b69c11b487334ef02ce7bfcdeb36c._comment new file mode 100644 index 000000000..52354d7dc --- /dev/null +++ b/doc/bugs/SanityCheckerStartup_crashed/comment_1_f30b69c11b487334ef02ce7bfcdeb36c._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="108.236.230.124" + subject="comment 1" + date="2014-06-04T18:07:11Z" + content=""" +This was already fixed in [[!commit 9c0f3ae7e13cc8ed43ac73fbab565e07c10d2c90]]. +"""]] -- cgit v1.2.3 From 16064cae057ded011f1396228d4065030177db8c Mon Sep 17 00:00:00 2001 From: "http://joeyh.name/" Date: Wed, 4 Jun 2014 18:08:39 +0000 Subject: Added a comment --- .../comment_3_051e39129a38e439f24703385f503cf4._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/bugs/android_4.3_install_failed_/comment_3_051e39129a38e439f24703385f503cf4._comment diff --git a/doc/bugs/android_4.3_install_failed_/comment_3_051e39129a38e439f24703385f503cf4._comment b/doc/bugs/android_4.3_install_failed_/comment_3_051e39129a38e439f24703385f503cf4._comment new file mode 100644 index 000000000..3f6e86ce4 --- /dev/null +++ b/doc/bugs/android_4.3_install_failed_/comment_3_051e39129a38e439f24703385f503cf4._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="108.236.230.124" + subject="comment 3" + date="2014-06-04T18:08:39Z" + content=""" +I asked if your Android device has an eqivilant directory to /sdcard that you can write to. If so, I can fix git-annex to use that directory. But you need to tell me what it is first! +"""]] -- cgit v1.2.3 From 75e72a85d734843f4bf12c84187455881c480330 Mon Sep 17 00:00:00 2001 From: "http://joeyh.name/" Date: Wed, 4 Jun 2014 18:14:19 +0000 Subject: Added a comment --- .../comment_1_48f71865b65db4574a10e5c32ee22197._comment | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 doc/bugs/unwanted_repository_version_upgrades/comment_1_48f71865b65db4574a10e5c32ee22197._comment diff --git a/doc/bugs/unwanted_repository_version_upgrades/comment_1_48f71865b65db4574a10e5c32ee22197._comment b/doc/bugs/unwanted_repository_version_upgrades/comment_1_48f71865b65db4574a10e5c32ee22197._comment new file mode 100644 index 000000000..2eee18f1a --- /dev/null +++ b/doc/bugs/unwanted_repository_version_upgrades/comment_1_48f71865b65db4574a10e5c32ee22197._comment @@ -0,0 +1,12 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="108.236.230.124" + subject="comment 1" + date="2014-06-04T18:14:19Z" + content=""" +If your repository is not using direct mode, it's completely safe to edit .git/config and set the version back to 3. There is no change between 3 and 5 for indirect mode repositories. + +Unfortunately, using git-annex version 5 will automatically upgrade the repository to 5 again. In general, I only want git-annex to support one version at a time, to avoid complicating the code. I did try leaving the indirect mode repositories at v3, but that didn't work out (some details in [[!commit b1d7474c1d713a5b422948178abb4e5f39e85096]]). + +I kind of think that part of the problem is that you're using git-annex repositories accessed via a file server. If your server had git-annex installed on it and the clients talked to it only by sshing in and running git-annex-shell, it would not matter if the clients had a newer version, because they'd never access the central repository directly. +"""]] -- cgit v1.2.3 From 320597bfddc1b0726d6e5a9386df7084ed348aae Mon Sep 17 00:00:00 2001 From: "http://joeyh.name/" Date: Wed, 4 Jun 2014 18:21:13 +0000 Subject: Added a comment --- .../comment_1_a3fbae205c0312436f8861f432643811._comment | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 doc/forum/Can_git_annex___40__mostly__41___be_an_Ubuntu_One___40__or_Dropbox...__41___substitute__63__/comment_1_a3fbae205c0312436f8861f432643811._comment diff --git a/doc/forum/Can_git_annex___40__mostly__41___be_an_Ubuntu_One___40__or_Dropbox...__41___substitute__63__/comment_1_a3fbae205c0312436f8861f432643811._comment b/doc/forum/Can_git_annex___40__mostly__41___be_an_Ubuntu_One___40__or_Dropbox...__41___substitute__63__/comment_1_a3fbae205c0312436f8861f432643811._comment new file mode 100644 index 000000000..a5baa31f3 --- /dev/null +++ b/doc/forum/Can_git_annex___40__mostly__41___be_an_Ubuntu_One___40__or_Dropbox...__41___substitute__63__/comment_1_a3fbae205c0312436f8861f432643811._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="108.236.230.124" + subject="comment 1" + date="2014-06-04T18:21:13Z" + content=""" +your box.com repository only stores encrypted file contents, it does not include the git repository. So you need to either set up XMPP, which will allow the clients to sync while they're turned on, or you need to put a git repository on a remote server, which the clients can use to sync anytime. + +Recent versions of git-annex allow encrypting the git repository. Use the \"remote server\" option in the webapp UI to set it up. +"""]] -- cgit v1.2.3