From 3b0fe55661fbf42ae9531af275de44b1832a4da2 Mon Sep 17 00:00:00 2001 From: "http://meep.pl/" Date: Fri, 9 Nov 2012 08:54:12 +0000 Subject: Added a comment: git-remote-helpers --- .../comment_1_e95efb23eb2e67e3f11a5c7de56424a7._comment | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 doc/design/assistant/blog/day_122__xmpp_pairing/comment_1_e95efb23eb2e67e3f11a5c7de56424a7._comment (limited to 'doc') diff --git a/doc/design/assistant/blog/day_122__xmpp_pairing/comment_1_e95efb23eb2e67e3f11a5c7de56424a7._comment b/doc/design/assistant/blog/day_122__xmpp_pairing/comment_1_e95efb23eb2e67e3f11a5c7de56424a7._comment new file mode 100644 index 000000000..990fa816e --- /dev/null +++ b/doc/design/assistant/blog/day_122__xmpp_pairing/comment_1_e95efb23eb2e67e3f11a5c7de56424a7._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="http://meep.pl/" + ip="193.219.28.34" + subject="git-remote-helpers" + date="2012-11-09T08:54:11Z" + content=""" +It seems that xmpp::user@host (with double colon) would cause git to try to use a remote-xmpp helper. +Wouldn't it be a way to have the remote address (if not really URL) set and not be treated as ssh? + +"""]] -- cgit v1.2.3 From 25431303c4d86d5e3587cd6db1b9b9c984967412 Mon Sep 17 00:00:00 2001 From: "https://www.google.com/accounts/o8/id?id=AItOawlYziqspADKgTfzHnQvD9DmNG6OycIoEh4" Date: Fri, 9 Nov 2012 13:37:20 +0000 Subject: --- ...ssistant_with___34__host:port__34___syntax.mdwn | 27 ++++++++++++++++++++++ 1 file changed, 27 insertions(+) create mode 100644 doc/bugs/can_not_add_ssh_remote_to_assistant_with___34__host:port__34___syntax.mdwn (limited to 'doc') diff --git a/doc/bugs/can_not_add_ssh_remote_to_assistant_with___34__host:port__34___syntax.mdwn b/doc/bugs/can_not_add_ssh_remote_to_assistant_with___34__host:port__34___syntax.mdwn new file mode 100644 index 000000000..9118a6c26 --- /dev/null +++ b/doc/bugs/can_not_add_ssh_remote_to_assistant_with___34__host:port__34___syntax.mdwn @@ -0,0 +1,27 @@ +What steps will reproduce the problem? + +* Start the assistant +* try to add a remote server (ssh) which is not on port 22. E.g. using myhost:1234 +* after a rather long time the connection fails + + +What is the expected output? What do you see instead? + +it would be nice if this syntax was supported, or if an (optional) port field was provided. +second best solution: inform the user that "myhost:1234" is not the expected format. +third best solution (already in place) fail with "some error message". + + + + +What version of git-annex are you using? On what operating system? + +3.20121016 on Ubuntu 12.04 (in future maybe also on home nas with wheezy) + + +Please provide any additional information below. + +Thanks for a nice program and all your work on debian! +this is not really a bug more of a wishlist feature. + + -- cgit v1.2.3 From 982249d93c25204d5d3866bf128c7d7cbfd935d5 Mon Sep 17 00:00:00 2001 From: "https://www.google.com/accounts/o8/id?id=AItOawmBUR4O9mofxVbpb8JV9mEbVfIYv670uJo" Date: Fri, 9 Nov 2012 14:04:57 +0000 Subject: Added a comment --- .../comment_1_397eb359c3f8ef30460a9556b6f55848._comment | 14 ++++++++++++++ 1 file changed, 14 insertions(+) create mode 100644 doc/bugs/can_not_add_ssh_remote_to_assistant_with___34__host:port__34___syntax/comment_1_397eb359c3f8ef30460a9556b6f55848._comment (limited to 'doc') diff --git a/doc/bugs/can_not_add_ssh_remote_to_assistant_with___34__host:port__34___syntax/comment_1_397eb359c3f8ef30460a9556b6f55848._comment b/doc/bugs/can_not_add_ssh_remote_to_assistant_with___34__host:port__34___syntax/comment_1_397eb359c3f8ef30460a9556b6f55848._comment new file mode 100644 index 000000000..991a7483d --- /dev/null +++ b/doc/bugs/can_not_add_ssh_remote_to_assistant_with___34__host:port__34___syntax/comment_1_397eb359c3f8ef30460a9556b6f55848._comment @@ -0,0 +1,14 @@ +[[!comment format=mdwn + username="https://www.google.com/accounts/o8/id?id=AItOawmBUR4O9mofxVbpb8JV9mEbVfIYv670uJo" + nickname="Justin" + subject="comment 1" + date="2012-11-09T14:04:57Z" + content=""" +edit ~/.ssh/config. add + + Host myhost + Port 1234 + + +now you never have to specify the port again(for ssh,scp,rsync,etc) +"""]] -- cgit v1.2.3 From dcbdd3a069b9c58d53eea1b7a152995505597ac3 Mon Sep 17 00:00:00 2001 From: "http://phil.0x539.de/" Date: Fri, 9 Nov 2012 14:05:30 +0000 Subject: Added a comment: How to deal with offline messages being eaten? --- .../comment_1_c2b0617a2fc3dc4f19a6be6947913842._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/design/assistant/blog/day_114__xmpp/comment_1_c2b0617a2fc3dc4f19a6be6947913842._comment (limited to 'doc') diff --git a/doc/design/assistant/blog/day_114__xmpp/comment_1_c2b0617a2fc3dc4f19a6be6947913842._comment b/doc/design/assistant/blog/day_114__xmpp/comment_1_c2b0617a2fc3dc4f19a6be6947913842._comment new file mode 100644 index 000000000..a391435c4 --- /dev/null +++ b/doc/design/assistant/blog/day_114__xmpp/comment_1_c2b0617a2fc3dc4f19a6be6947913842._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="http://phil.0x539.de/" + nickname="Philipp Kern" + subject="How to deal with offline messages being eaten?" + date="2012-11-09T14:05:30Z" + content=""" +How do you avoid eating up normal text messages when git-annex is the only client left? Granted, Google Talk does some additional magic so that it shows you the history when connecting with the web page client. But with other servers it would be inconvenient if new messages weren't saved as offline messages but sent to the dæmon instead. +"""]] -- cgit v1.2.3 From 80c9a8d0dad62145d5a734b043aa008ccdc03a48 Mon Sep 17 00:00:00 2001 From: "https://www.google.com/accounts/o8/id?id=AItOawn7gQ1zZDdWhXy9H51W2krZYShNmKL3qfM" Date: Fri, 9 Nov 2012 14:25:17 +0000 Subject: --- ...moving_files_not_found_by_git_annex_unused.mdwn | 29 ++++++++++++++++++++++ 1 file changed, 29 insertions(+) create mode 100644 doc/forum/Removing_files_not_found_by_git_annex_unused.mdwn (limited to 'doc') diff --git a/doc/forum/Removing_files_not_found_by_git_annex_unused.mdwn b/doc/forum/Removing_files_not_found_by_git_annex_unused.mdwn new file mode 100644 index 000000000..ce0aedc51 --- /dev/null +++ b/doc/forum/Removing_files_not_found_by_git_annex_unused.mdwn @@ -0,0 +1,29 @@ +Hi, + +I've removed some large files with git remove, but seem to be unable to remove the corresponding annex content. + +Example: + +kheymann@corax:~/annex$ find -name "*s24576--10daa3d9007edad720dc057e4272a9c6cda930bef34a83e3bc1d93f1c55b9cac" + +./.git/annex/objects/jF/j7/SHA256-s24576--10daa3d9007edad720dc057e4272a9c6cda930bef34a83e3bc1d93f1c55b9cac + +./.git/annex/objects/jF/j7/SHA256-s24576--10daa3d9007edad720dc057e4272a9c6cda930bef34a83e3bc1d93f1c55b9cac/SHA256-s24576--10daa3d9007edad720dc057e4272a9c6cda930bef34a83e3bc1d93f1c55b9cac + +kheymann@corax:~/annex$ git annex dropkey -vvv --backend SHA256 s24576--10daa3d9007edad720dc057e4272a9c6cda930bef34a83e3bc1d93f1c55b9cac + +No output but the files remain in the annex. Git annex fsck and git annex unused run without listing files to be removes. What can I do apart from deleting the files manually from the annex? + +Some info: + + kheymann@corax:~/annex$ git annex version + git-annex version: 3.20121017 + local repository version: 3 + default repository version: 3 + supported repository versions: 3 + upgrade supported from repository versions: 0 1 2 + +Any hints? + +Best, +Karsten -- cgit v1.2.3