From f207fb961aa46b7de397b7fa76def81e5b5cc769 Mon Sep 17 00:00:00 2001 From: "http://joeyh.name/" Date: Sat, 9 Nov 2013 18:07:56 +0000 Subject: [PATCH 1/2] Added a comment --- ...mment_3_3a8a7f51cb04a92c576549d379b57248._comment | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 doc/forum/Permission_denied___40__publickey__41___On_second_Step_...___63__/comment_3_3a8a7f51cb04a92c576549d379b57248._comment diff --git a/doc/forum/Permission_denied___40__publickey__41___On_second_Step_...___63__/comment_3_3a8a7f51cb04a92c576549d379b57248._comment b/doc/forum/Permission_denied___40__publickey__41___On_second_Step_...___63__/comment_3_3a8a7f51cb04a92c576549d379b57248._comment new file mode 100644 index 0000000000..546f647edb --- /dev/null +++ b/doc/forum/Permission_denied___40__publickey__41___On_second_Step_...___63__/comment_3_3a8a7f51cb04a92c576549d379b57248._comment @@ -0,0 +1,12 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="209.250.56.246" + subject="comment 3" + date="2013-11-09T18:07:56Z" + content=""" +Well, it does look like your git-annex did not pass the port to the second command. + +What version are you using? I've just tested with a ssh server only listening on 2222 and it used the port throughout. + +You might try upgrading to a recent version. I know that version 4.20130627, at least, had a bug with the ssh port. +"""]] From 491332ad9bf3d86db11347e2737c0b9012d75354 Mon Sep 17 00:00:00 2001 From: "http://joeyh.name/" Date: Sat, 9 Nov 2013 18:18:49 +0000 Subject: [PATCH 2/2] Added a comment --- ...mment_1_a35b35c7927640f21d47c3df4f91dabb._comment | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 doc/forum/Help_on_my_usecase/comment_1_a35b35c7927640f21d47c3df4f91dabb._comment diff --git a/doc/forum/Help_on_my_usecase/comment_1_a35b35c7927640f21d47c3df4f91dabb._comment b/doc/forum/Help_on_my_usecase/comment_1_a35b35c7927640f21d47c3df4f91dabb._comment new file mode 100644 index 0000000000..25116a7c43 --- /dev/null +++ b/doc/forum/Help_on_my_usecase/comment_1_a35b35c7927640f21d47c3df4f91dabb._comment @@ -0,0 +1,12 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="209.250.56.246" + subject="comment 1" + date="2013-11-09T18:18:49Z" + content=""" +An incremental backup is supposed to drop content once it reaches a full backup. But, the assistant can only do that if it's able to verify that the full backup drive (or some other repository it can access) has a file, at the same time it's dropping it from the incremental backup drive. If you don't have both the incremental and full backup drives plugged in at the same time, you could consider making git-annex [[trust]] the full backup drive, which would avoid this explicit check. + +It sounds like you want a non-bare git repository on the 2.5\" drive. The assistant does not currently support setting that up, but you can do it by just using `git clone` as shown in the [[walkthrough]]. + +I'm not clear on what doesn't work when you connect the 2.5\" drive to your desktop. +"""]]