From 6cef6b49ba6eb32a1fa922d76a1ca051d1ae44f1 Mon Sep 17 00:00:00 2001 From: "http://joeyh.name/" Date: Fri, 21 Feb 2014 17:36:03 +0000 Subject: Added a comment --- .../comment_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 000000000..050127c24 --- /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. +"""]] -- cgit v1.2.3 From 3a1bd44d8a09247167a3aabab87737a85526424f Mon Sep 17 00:00:00 2001 From: "http://grossmeier.net/" Date: Fri, 21 Feb 2014 17:53:02 +0000 Subject: 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 000000000..65128b72c --- /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 ...... +"""]] -- cgit v1.2.3 From c6b64cd3b10fac3415b0e533979e96e8fbe2764e 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: 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 000000000..60aea0bdd --- /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. +"""]] -- cgit v1.2.3 From 7d82f8010614df75d24cbcedf4bd54f6b7fc1289 Mon Sep 17 00:00:00 2001 From: Greg Grossmeier Date: Fri, 21 Feb 2014 13:28:17 -0800 Subject: 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 000000000..ddce8eca0 --- /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. -- cgit v1.2.3 From d31bf5cc03ab2f6d0328929f219ebc3cbaf2a7ec Mon Sep 17 00:00:00 2001 From: Greg Grossmeier Date: Fri, 21 Feb 2014 13:30:11 -0800 Subject: 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 ddce8eca0..7101d578f 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. -- cgit v1.2.3 From 1f5fa851948bb47f3346d444f9b1099fdc43d83c Mon Sep 17 00:00:00 2001 From: "http://joeyh.name/" Date: Fri, 21 Feb 2014 21:36:14 +0000 Subject: 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 000000000..16139c78d --- /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). +"""]] -- cgit v1.2.3 From f4546620ebbb58fd91fa85fb9212ce493d8ba2b0 Mon Sep 17 00:00:00 2001 From: Dennis Date: Fri, 21 Feb 2014 21:51:55 +0000 Subject: --- doc/forum/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 000000000..b0fe9ddaa --- /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. -- cgit v1.2.3 From 1b0310840506d033aa53ac0d36406ec4fbe5a789 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: 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 000000000..591d4e80f --- /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! +"""]] -- cgit v1.2.3 From 37efb733070169238e453ce979904e5d440b7099 Mon Sep 17 00:00:00 2001 From: "http://grossmeier.net/" Date: Fri, 21 Feb 2014 22:11:16 +0000 Subject: 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 000000000..827b99afa --- /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 :) +"""]] -- cgit v1.2.3 From 00fdde0fec260af4fa861efa5e769f75a7bdea86 Mon Sep 17 00:00:00 2001 From: "http://joeyh.name/" Date: Fri, 21 Feb 2014 22:34:14 +0000 Subject: 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 000000000..ed7e4d3b6 --- /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. +"""]] -- cgit v1.2.3