From 47826e4ef87f1674266256f678117945f23ea1f5 Mon Sep 17 00:00:00 2001 From: "http://joeyh.name/" Date: Wed, 17 Jul 2013 18:54:47 +0000 Subject: [PATCH 1/7] Added a comment --- ...mment_1_dd792bd98a48554a65150c06401ed3e5._comment | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 doc/bugs/Should_try_again_when_network_fails___40__esp._DNS__41__/comment_1_dd792bd98a48554a65150c06401ed3e5._comment diff --git a/doc/bugs/Should_try_again_when_network_fails___40__esp._DNS__41__/comment_1_dd792bd98a48554a65150c06401ed3e5._comment b/doc/bugs/Should_try_again_when_network_fails___40__esp._DNS__41__/comment_1_dd792bd98a48554a65150c06401ed3e5._comment new file mode 100644 index 0000000000..620f5e82e4 --- /dev/null +++ b/doc/bugs/Should_try_again_when_network_fails___40__esp._DNS__41__/comment_1_dd792bd98a48554a65150c06401ed3e5._comment @@ -0,0 +1,12 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="4.154.4.90" + subject="comment 1" + date="2013-07-17T18:54:47Z" + content=""" +Trying again one time does not seem like it would help, given the example you show. Trying multiple times by default would, I think, be annoying in lots of use cases where one just wants to get whatever is available, and having it get stuck retrying to download a file from a remote that is offline would not be desired when it could move on and get another file from a remote that is online. + +I'm willing to consider some kind of option to control how much it retries on error. But I'm not 100% sold on it being better than a simple loop. At least in most cases, using a gpg agent and a loop would work. I suppose the case it would not work as well is if enough time has elapsed for the gpg agent to re-lock the key. + +One approach that might work well is to add a --retry-failures-at-end option. It turns out that all failed downloads are already logged (the assistant uses this to automatically retry them), and so it would be easy to add. And rather than retrying immediately after a failure, when transferring multiple files, this puts some space in between, in which the problem may correct itself. +"""]] From 12210e3f4e98df2a87af9c91f3e3e8a9e64d914e Mon Sep 17 00:00:00 2001 From: "http://joeyh.name/" Date: Wed, 17 Jul 2013 18:57:12 +0000 Subject: [PATCH 2/7] Added a comment --- ...comment_6_410a7296c2cee16d3d5bb618a5a41c1d._comment | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 doc/forum/safely_dropping_git-annex_history/comment_6_410a7296c2cee16d3d5bb618a5a41c1d._comment diff --git a/doc/forum/safely_dropping_git-annex_history/comment_6_410a7296c2cee16d3d5bb618a5a41c1d._comment b/doc/forum/safely_dropping_git-annex_history/comment_6_410a7296c2cee16d3d5bb618a5a41c1d._comment new file mode 100644 index 0000000000..05ac273616 --- /dev/null +++ b/doc/forum/safely_dropping_git-annex_history/comment_6_410a7296c2cee16d3d5bb618a5a41c1d._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="4.154.4.90" + subject="comment 6" + date="2013-07-17T18:57:12Z" + content=""" +You can use `git annex fsck --from remote` to verify that every file location tracking thinks is on the remote still is. It's innefficient though -- it has to download the whole file to check the special remote still has the right content! That transfer can be avoided by adding --fast. + +This is documented in the man page. :) +"""]] From 477322448531be554d154bc54b50b6eb3cd53f91 Mon Sep 17 00:00:00 2001 From: "http://joeyh.name/" Date: Wed, 17 Jul 2013 18:59:03 +0000 Subject: [PATCH 3/7] Added a comment --- .../comment_7_42cf492fc98a9eba8176387749ef12e0._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/forum/safely_dropping_git-annex_history/comment_7_42cf492fc98a9eba8176387749ef12e0._comment diff --git a/doc/forum/safely_dropping_git-annex_history/comment_7_42cf492fc98a9eba8176387749ef12e0._comment b/doc/forum/safely_dropping_git-annex_history/comment_7_42cf492fc98a9eba8176387749ef12e0._comment new file mode 100644 index 0000000000..5c10b988cd --- /dev/null +++ b/doc/forum/safely_dropping_git-annex_history/comment_7_42cf492fc98a9eba8176387749ef12e0._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="4.154.4.90" + subject="comment 7" + date="2013-07-17T18:59:03Z" + content=""" +I don't see any reason why squashing git-annex branch history would not work. If you squash it to the same sha in each clone, things would be very happy, but even if you squash it to different shas, the union merge should result in those different versions of the same data automatically merging together. +"""]] From 77ff0941766800a1d2e57762ac8100b874dd07b2 Mon Sep 17 00:00:00 2001 From: "http://joeyh.name/" Date: Wed, 17 Jul 2013 19:06:31 +0000 Subject: [PATCH 4/7] Added a comment --- ...omment_20_81940ea56ace3dcd5fa84dfccd88ad96._comment | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 doc/Android/comment_20_81940ea56ace3dcd5fa84dfccd88ad96._comment diff --git a/doc/Android/comment_20_81940ea56ace3dcd5fa84dfccd88ad96._comment b/doc/Android/comment_20_81940ea56ace3dcd5fa84dfccd88ad96._comment new file mode 100644 index 0000000000..ed4d6e0b0b --- /dev/null +++ b/doc/Android/comment_20_81940ea56ace3dcd5fa84dfccd88ad96._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="4.154.4.90" + subject="comment 20" + date="2013-07-17T19:06:31Z" + content=""" +@frioux the webapp has a \"ssh server\" option that will set up a ssh key and use it for passwordless data transfer to a ssh server. You have to enter your password twice in the git-annex terminal app, and then it's set up. + +The openssh included in the git-annex app fully supports everything you can usually do with ssh keys, so you can also set this up by hand. +"""]] From 6d09f52f8efa189c16dbb5346802dc72a2891cdc Mon Sep 17 00:00:00 2001 From: "http://joeyh.name/" Date: Wed, 17 Jul 2013 19:06:59 +0000 Subject: [PATCH 5/7] Added a comment --- ...comment_1_3e95ac2e67451f953cf0538094109f8b._comment | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 doc/forum/Sync_without_jabber_account/comment_1_3e95ac2e67451f953cf0538094109f8b._comment diff --git a/doc/forum/Sync_without_jabber_account/comment_1_3e95ac2e67451f953cf0538094109f8b._comment b/doc/forum/Sync_without_jabber_account/comment_1_3e95ac2e67451f953cf0538094109f8b._comment new file mode 100644 index 0000000000..1a601848c1 --- /dev/null +++ b/doc/forum/Sync_without_jabber_account/comment_1_3e95ac2e67451f953cf0538094109f8b._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="4.154.4.90" + subject="comment 1" + date="2013-07-17T19:06:59Z" + content=""" +We don't currently have a way to store a git repository on box.com, and you need such a git repo on a server somewhere if you're not using Jabber. + +Of course you can mount the box.com, using either davfs2 or something else, and put a bare git repository in its directory, and if you set this up on multiple computers, it might just work (or they might both try to write to it at the same time and fail.. I have not tried). +"""]] From 3f6a855dca2fba57b0af436aca36a89823dc3e33 Mon Sep 17 00:00:00 2001 From: "http://joeyh.name/" Date: Wed, 17 Jul 2013 19:11:38 +0000 Subject: [PATCH 6/7] Added a comment --- ...mment_1_5b6e0b749b01a97a6b52a2c1cca6e35a._comment | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 doc/forum/git_annex_copy_--fast_--to_blah_much_slower_than_--from_blah/comment_1_5b6e0b749b01a97a6b52a2c1cca6e35a._comment diff --git a/doc/forum/git_annex_copy_--fast_--to_blah_much_slower_than_--from_blah/comment_1_5b6e0b749b01a97a6b52a2c1cca6e35a._comment b/doc/forum/git_annex_copy_--fast_--to_blah_much_slower_than_--from_blah/comment_1_5b6e0b749b01a97a6b52a2c1cca6e35a._comment new file mode 100644 index 0000000000..90d4292789 --- /dev/null +++ b/doc/forum/git_annex_copy_--fast_--to_blah_much_slower_than_--from_blah/comment_1_5b6e0b749b01a97a6b52a2c1cca6e35a._comment @@ -0,0 +1,12 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="4.154.4.90" + subject="comment 1" + date="2013-07-17T19:11:38Z" + content=""" +How many files are in the directory tree you're copying? + +`copy --fast --to` does indeed avoid the check to see if the remote already has the file before copying it. + +However, it still needs to look in the location log to see which files are already present on the remote. Whereas `copy --from` can do a single stat of the file on disk to see if it's present in the local repo. Location log lookups are about as fast as I can make them, but they still require requesting info from out of the git repository. If you have a lot of files this otherwise minor difference in speed can stack up.. +"""]] From 2521a9fe2687df6c6cd3058b23207ab79b1181a7 Mon Sep 17 00:00:00 2001 From: "http://joeyh.name/" Date: Wed, 17 Jul 2013 19:12:50 +0000 Subject: [PATCH 7/7] Added a comment --- .../comment_3_54ae097d30bb7a49fe151f38c9bac033._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/bugs/TransferScanner_crash_on_Android/comment_3_54ae097d30bb7a49fe151f38c9bac033._comment diff --git a/doc/bugs/TransferScanner_crash_on_Android/comment_3_54ae097d30bb7a49fe151f38c9bac033._comment b/doc/bugs/TransferScanner_crash_on_Android/comment_3_54ae097d30bb7a49fe151f38c9bac033._comment new file mode 100644 index 0000000000..bb31e7f866 --- /dev/null +++ b/doc/bugs/TransferScanner_crash_on_Android/comment_3_54ae097d30bb7a49fe151f38c9bac033._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="4.154.4.90" + subject="comment 3" + date="2013-07-17T19:12:49Z" + content=""" +I don't see how git annex fsck could resolve the corruption, which appeared to be of data from the git repository, not the git-annex content store. Did you try `git fsck`? +"""]]