diff --git a/doc/bugs/git-annex_deletes_file_when_using___34__git_annex_get__34___after___34__git_annex_addurl_--file__34__/comment_2_c683d729fb0b3285ba9946539fe50d0d._comment b/doc/bugs/git-annex_deletes_file_when_using___34__git_annex_get__34___after___34__git_annex_addurl_--file__34__/comment_2_c683d729fb0b3285ba9946539fe50d0d._comment new file mode 100644 index 0000000000..8c757b8a3c --- /dev/null +++ b/doc/bugs/git-annex_deletes_file_when_using___34__git_annex_get__34___after___34__git_annex_addurl_--file__34__/comment_2_c683d729fb0b3285ba9946539fe50d0d._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="https://sunny256.wordpress.com/" + nickname="sunny256" + subject="Thanks" + date="2015-05-07T14:20:49Z" + content=""" +Thank you for looking into this and coming up with a fix. Awesome. :) +"""]] diff --git a/doc/bugs/webapp_fails_to_connect_to_ssh_repository___40__windows__41__/comment_1_c89c2fcd8d93bc64b80749b4207a3ebd._comment b/doc/bugs/webapp_fails_to_connect_to_ssh_repository___40__windows__41__/comment_1_c89c2fcd8d93bc64b80749b4207a3ebd._comment new file mode 100644 index 0000000000..6db718bf2e --- /dev/null +++ b/doc/bugs/webapp_fails_to_connect_to_ssh_repository___40__windows__41__/comment_1_c89c2fcd8d93bc64b80749b4207a3ebd._comment @@ -0,0 +1,9 @@ +[[!comment format=mdwn + username="anton" + subject="me too" + date="2015-05-07T09:50:09Z" + content=""" +I get similar results on Windows, but I only use the command line. For some reason git-annex ignores the ssh-agent settings (SSH_AUTH_SOCK=...) and uses the wrong path for the ssh config dir -- /home/username/.ssh (that probably doesn't exist) -- instead of c:/Users/username/.ssh (or whatever it really is). Your issue is probably that ssh wrongly looks for known_hosts in /home/username/.ssh and asks whether you wan't to accept the unknown host key. + +SSH works when ran by git itself (like git clone/push/fetch), also for rsync, but seemingly not git-annex. +"""]] diff --git a/doc/forum/How_to_find_deleted_files_that_I_know_have_been_backed_up__63__/comment_5_94aca10f84783f35d927dbefbeba263a._comment b/doc/forum/How_to_find_deleted_files_that_I_know_have_been_backed_up__63__/comment_5_94aca10f84783f35d927dbefbeba263a._comment new file mode 100644 index 0000000000..77cf1c2895 --- /dev/null +++ b/doc/forum/How_to_find_deleted_files_that_I_know_have_been_backed_up__63__/comment_5_94aca10f84783f35d927dbefbeba263a._comment @@ -0,0 +1,16 @@ +[[!comment format=mdwn + username="http://hendry.iki.fi/" + nickname="Kai Hendry" + subject="Two more questions" + date="2015-05-07T07:40:41Z" + content=""" +How do I undelete in my case then? I.e. not `git checkout ` to find where they are. + +`git revert c53dbdd9bd7879d68635a2adc81a7bc59a84c5ea` + + + +Assuming I make no effort to undelete or recover the files: + +The (deleted) files I have copies of on my other two hard drives. Do they detect I've deleted the files and just clean up? How does that process work? +"""]] diff --git a/doc/forum/rsync_regression_on_Windows.mdwn b/doc/forum/rsync_regression_on_Windows.mdwn new file mode 100644 index 0000000000..d0bc0f14d1 --- /dev/null +++ b/doc/forum/rsync_regression_on_Windows.mdwn @@ -0,0 +1,16 @@ +I'm on Windows 7 and msysgit. The rsync that comes with the git-annex installer downloaded on January 19 2015 works fine (rsync version 3.0.9, protocol version 30; git annex version 5.20150113-gcf247cf). The rsync that comes with the current git-annex installer errors out (rsync version 3.1.1 protocol version 31; git annex v ersion 5.20150420-gb0ebb23). I don't think it's a version/protocol mismatch, as I get the error against a server with the same version and protocol. + +[[!format sh """ +$ rsync -rvvp anton@myhost:wtmp/ wtmp +opening connection using: ssh -l anton myhost rsync --server --sender -vv +pre.iLsfx . wtmp/ (10 args) +rsync: connection unexpectedly closed (0 bytes received so far) [Receiver] +rsync error: error in rsync protocol data stream (code 12) at io.c(226) [Receiver=3.1.1] + +$ ssh -l anton myhost rsync --version +rsync version 3.1.1 protocol version 31 +... + +"""]] + +Bug or user error?