From 6aa9f1f788c57b5464e43e5f98b0aaafe6dcd09e Mon Sep 17 00:00:00 2001 From: "http://joeyh.name/" Date: Fri, 21 Feb 2014 17:36:03 +0000 Subject: [PATCH 01/10] Added a comment --- ...mment_1_b1a9420974e2e50c9c86a379ad62502c._comment | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 doc/forum/Can_not_delete_Repository/comment_1_b1a9420974e2e50c9c86a379ad62502c._comment diff --git a/doc/forum/Can_not_delete_Repository/comment_1_b1a9420974e2e50c9c86a379ad62502c._comment b/doc/forum/Can_not_delete_Repository/comment_1_b1a9420974e2e50c9c86a379ad62502c._comment new file mode 100644 index 0000000000..050127c24b --- /dev/null +++ b/doc/forum/Can_not_delete_Repository/comment_1_b1a9420974e2e50c9c86a379ad62502c._comment @@ -0,0 +1,12 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="209.250.56.172" + subject="comment 1" + date="2014-02-21T17:36:03Z" + content=""" +Marking a repository as dead does not mean it is deleted. The way this is supposed to work, using the webapp is you tell it to start deleting the repository, which causes it to mark it as dead, and also, crucially, puts it into the \"unwanted\" group. This does not remove it from the list yet, but it causes all files located in the repository to be moved off it (assuming the repository can still be accessed). + +Then once the webapp detects that the repository is empty it will prompt you to continue the deletion process and truely remove it. It can take quite a while for the webapp to get around to this last step, since it's done during the expensive transfer scan, which it tries to avoid running unnecessarily. + +In any case, you can always edit .git/config and delete the remote, which should make the webapp no longer show it, as long as it's marked as dead. +"""]] From 57e3b037ede147663cd0f20b2d7f493bc882bc8f Mon Sep 17 00:00:00 2001 From: "http://grossmeier.net/" Date: Fri, 21 Feb 2014 17:53:02 +0000 Subject: [PATCH 02/10] Added a comment: confirmed --- .../comment_6_0fbe528a57552622e8128196ad80c863._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/tips/using_Amazon_Glacier/comment_6_0fbe528a57552622e8128196ad80c863._comment diff --git a/doc/tips/using_Amazon_Glacier/comment_6_0fbe528a57552622e8128196ad80c863._comment b/doc/tips/using_Amazon_Glacier/comment_6_0fbe528a57552622e8128196ad80c863._comment new file mode 100644 index 0000000000..65128b72cd --- /dev/null +++ b/doc/tips/using_Amazon_Glacier/comment_6_0fbe528a57552622e8128196ad80c863._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="http://grossmeier.net/" + nickname="greg" + subject="confirmed" + date="2014-02-21T17:53:02Z" + content=""" +Yeah, I choose no encryption for this one for worst case scenario reasons (I still want photos of my kid even if I loss my gpg key and my house burns down). Now about setting up http://git.kitenet.net/?p=gpg.git;a=blob;f=README.sss;hb=HEAD ...... +"""]] From f0fb81445f2eba3808691b94d9561b79c3774d50 Mon Sep 17 00:00:00 2001 From: "https://www.google.com/accounts/o8/id?id=AItOawnBJ6Dv1glxzzi4qIzGFNa6F-mfHIvv9Ck" Date: Fri, 21 Feb 2014 18:44:10 +0000 Subject: [PATCH 03/10] Added a comment: Metadata? --- .../comment_2_dba1a1b0917332a1dee387b1183bd2cb._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/forum/Controlling_content_on_mobile_device/comment_2_dba1a1b0917332a1dee387b1183bd2cb._comment diff --git a/doc/forum/Controlling_content_on_mobile_device/comment_2_dba1a1b0917332a1dee387b1183bd2cb._comment b/doc/forum/Controlling_content_on_mobile_device/comment_2_dba1a1b0917332a1dee387b1183bd2cb._comment new file mode 100644 index 0000000000..60aea0bdda --- /dev/null +++ b/doc/forum/Controlling_content_on_mobile_device/comment_2_dba1a1b0917332a1dee387b1183bd2cb._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawnBJ6Dv1glxzzi4qIzGFNa6F-mfHIvv9Ck" + nickname="Jim" + subject="Metadata?" + date="2014-02-21T18:44:10Z" + content=""" +I suspect the new [metadata](http://git-annex.branchable.com/design/metadata/) support could be used to help implement this. +"""]] From d124228f1d3f667c3ffc04e7790bc99de2f53ace Mon Sep 17 00:00:00 2001 From: Greg Grossmeier Date: Fri, 21 Feb 2014 13:28:17 -0800 Subject: [PATCH 04/10] Added todo for handling ctrl c in transfers --- doc/todo/ctrl_c_handling.mdwn | 5 +++++ 1 file changed, 5 insertions(+) create mode 100644 doc/todo/ctrl_c_handling.mdwn diff --git a/doc/todo/ctrl_c_handling.mdwn b/doc/todo/ctrl_c_handling.mdwn new file mode 100644 index 0000000000..ddce8eca03 --- /dev/null +++ b/doc/todo/ctrl_c_handling.mdwn @@ -0,0 +1,5 @@ +Sometimes I start off a large file transfer to a new remote (a la "git-annex copy . --to glacier"). + +I believe all of the special remotes transfer the files one at a time, which is good, and provides a sensible place to interrupt a copy/move operation. + +Wish: When I press ctrl+c in the terminal, git-annex will catch that and finish it's current transfer and then exit. For the case where the file currently being transfered also needs to be killed (ie: it's a big .iso) then subsequent ctrl+c's can do that. From 2d17759be6d2f565ccda8d20145f4723e5fce0fe Mon Sep 17 00:00:00 2001 From: Greg Grossmeier Date: Fri, 21 Feb 2014 13:30:11 -0800 Subject: [PATCH 05/10] clarification --- doc/todo/ctrl_c_handling.mdwn | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/todo/ctrl_c_handling.mdwn b/doc/todo/ctrl_c_handling.mdwn index ddce8eca03..7101d578f5 100644 --- a/doc/todo/ctrl_c_handling.mdwn +++ b/doc/todo/ctrl_c_handling.mdwn @@ -2,4 +2,4 @@ Sometimes I start off a large file transfer to a new remote (a la "git-annex cop I believe all of the special remotes transfer the files one at a time, which is good, and provides a sensible place to interrupt a copy/move operation. -Wish: When I press ctrl+c in the terminal, git-annex will catch that and finish it's current transfer and then exit. For the case where the file currently being transfered also needs to be killed (ie: it's a big .iso) then subsequent ctrl+c's can do that. +Wish: When I press ctrl+c in the terminal, git-annex will catch that and finish it's current transfer and then exit cleanly (ie: no odd backtraces in the special remote code). For the case where the file currently being transfered also needs to be killed (ie: it's a big .iso) then subsequent ctrl+c's can do that. From 3585596b6f98697928572417dfa64139148d23ca Mon Sep 17 00:00:00 2001 From: "http://joeyh.name/" Date: Fri, 21 Feb 2014 21:36:14 +0000 Subject: [PATCH 06/10] Added a comment --- .../comment_1_3addbe33817db5de836c014287b14c07._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/todo/ctrl_c_handling/comment_1_3addbe33817db5de836c014287b14c07._comment diff --git a/doc/todo/ctrl_c_handling/comment_1_3addbe33817db5de836c014287b14c07._comment b/doc/todo/ctrl_c_handling/comment_1_3addbe33817db5de836c014287b14c07._comment new file mode 100644 index 0000000000..16139c78da --- /dev/null +++ b/doc/todo/ctrl_c_handling/comment_1_3addbe33817db5de836c014287b14c07._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="209.250.56.172" + subject="comment 1" + date="2014-02-21T21:36:14Z" + content=""" +This really depends on the remote, some can resume where they were interrupted, such as rsync, and some cannot, such as glacier (and, er, encrypted rsync). +"""]] From 8cce997e1f1769fb909964a9bc7990ef0f22531c Mon Sep 17 00:00:00 2001 From: Dennis Date: Fri, 21 Feb 2014 21:51:55 +0000 Subject: [PATCH 07/10] --- .../Find_files_that_lack_a_certain_field_in_metadata.mdwn | 5 +++++ 1 file changed, 5 insertions(+) create mode 100644 doc/forum/Find_files_that_lack_a_certain_field_in_metadata.mdwn diff --git a/doc/forum/Find_files_that_lack_a_certain_field_in_metadata.mdwn b/doc/forum/Find_files_that_lack_a_certain_field_in_metadata.mdwn new file mode 100644 index 0000000000..b0fe9ddaab --- /dev/null +++ b/doc/forum/Find_files_that_lack_a_certain_field_in_metadata.mdwn @@ -0,0 +1,5 @@ +Is there any way to find all files that do not have a certain field assigned in metadata. E.g. I want to find all files that do not have an author field set and + + git-annex find --not --metadata "author=*" + +doesn't give any results. From 9babfe70b745b0e67fc7c83bf204cc246e6a94cf Mon Sep 17 00:00:00 2001 From: "https://www.google.com/accounts/o8/id?id=AItOawmZgZuUhZlHpd_AbbcixY0QQiutb2I7GWY" Date: Fri, 21 Feb 2014 22:05:06 +0000 Subject: [PATCH 08/10] Added a comment --- .../comment_3_f199ac6ae2448949ef0779177cf0ef58._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/bugs/Mac_OS_git_version_still_too_old_for_.gitignore__63__/comment_3_f199ac6ae2448949ef0779177cf0ef58._comment diff --git a/doc/bugs/Mac_OS_git_version_still_too_old_for_.gitignore__63__/comment_3_f199ac6ae2448949ef0779177cf0ef58._comment b/doc/bugs/Mac_OS_git_version_still_too_old_for_.gitignore__63__/comment_3_f199ac6ae2448949ef0779177cf0ef58._comment new file mode 100644 index 0000000000..591d4e80f6 --- /dev/null +++ b/doc/bugs/Mac_OS_git_version_still_too_old_for_.gitignore__63__/comment_3_f199ac6ae2448949ef0779177cf0ef58._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawmZgZuUhZlHpd_AbbcixY0QQiutb2I7GWY" + nickname="Jimmy" + subject="comment 3" + date="2014-02-21T22:05:06Z" + content=""" +And yep, it's fixed in 5.20140221-g1a47f5f. Thanks guys! +"""]] From 3e680aea9ac425179b23dd3cb25a3262381d7bf1 Mon Sep 17 00:00:00 2001 From: "http://grossmeier.net/" Date: Fri, 21 Feb 2014 22:11:16 +0000 Subject: [PATCH 09/10] Added a comment: very remote specific --- .../comment_2_cc2776dc4805421180edcdf96a89fcaa._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/todo/ctrl_c_handling/comment_2_cc2776dc4805421180edcdf96a89fcaa._comment diff --git a/doc/todo/ctrl_c_handling/comment_2_cc2776dc4805421180edcdf96a89fcaa._comment b/doc/todo/ctrl_c_handling/comment_2_cc2776dc4805421180edcdf96a89fcaa._comment new file mode 100644 index 0000000000..827b99afa1 --- /dev/null +++ b/doc/todo/ctrl_c_handling/comment_2_cc2776dc4805421180edcdf96a89fcaa._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="http://grossmeier.net/" + nickname="greg" + subject="very remote specific" + date="2014-02-21T22:11:16Z" + content=""" +Yeah, this is very remote specific and probably means adding the functionality there as well (eg: in the glacier.py code, not only in git-annex haskell). Maybe I should file bugs there accordingly :) +"""]] From 4047c52ee1014185b6268e1bde82a70885da82cb Mon Sep 17 00:00:00 2001 From: "http://joeyh.name/" Date: Fri, 21 Feb 2014 22:34:14 +0000 Subject: [PATCH 10/10] Added a comment --- .../comment_3_8d7d357368987f5d5d59b4d8d99a0e06._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/todo/ctrl_c_handling/comment_3_8d7d357368987f5d5d59b4d8d99a0e06._comment diff --git a/doc/todo/ctrl_c_handling/comment_3_8d7d357368987f5d5d59b4d8d99a0e06._comment b/doc/todo/ctrl_c_handling/comment_3_8d7d357368987f5d5d59b4d8d99a0e06._comment new file mode 100644 index 0000000000..ed7e4d3b62 --- /dev/null +++ b/doc/todo/ctrl_c_handling/comment_3_8d7d357368987f5d5d59b4d8d99a0e06._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="209.250.56.172" + subject="comment 3" + date="2014-02-21T22:34:14Z" + content=""" +Hmm, I forget if it's possible for git-annex to mask SIGINT when it runs glacier or rsync, so that the child process does not receive it, but the parent git-annex does. +"""]]