diff options
author | Joey Hess <joey@kitenet.net> | 2014-05-21 13:20:23 -0400 |
---|---|---|
committer | Joey Hess <joey@kitenet.net> | 2014-05-21 13:20:23 -0400 |
commit | 5e3dd8768ae015c07a8c8a96a41f7798aea3b6ec (patch) | |
tree | 3a71ada95ec3b3d6ef494375d64728156728612f /doc/todo | |
parent | 88d1b41ebb903e32d624030af3eb5a5b0eacd843 (diff) |
move to todo
Diffstat (limited to 'doc/todo')
3 files changed, 71 insertions, 0 deletions
diff --git a/doc/todo/git-annex_ignores_GIT__95__SSH.mdwn b/doc/todo/git-annex_ignores_GIT__95__SSH.mdwn new file mode 100644 index 000000000..9af05496a --- /dev/null +++ b/doc/todo/git-annex_ignores_GIT__95__SSH.mdwn @@ -0,0 +1,39 @@ +### Please describe the problem. + +git uses environment variable GIT_SSH to determine SSH client. + +I set it to plink.exe because I extensively use pageant infrastructure and do NOT want to have 2 systems lying around. + +Unfortunately git-annex seems to ignore that. + +Even worse, it results in unpredicted behavior because the git part works (e.g. clone) whereas annex/rsync does not resulting in half-ok repositories without meaningful error messages. + +It only becomes evident when ssh.exe in the git repository is deleted. + +### What steps will reproduce the problem? + +Set %GIT_SSH% and remove ssh.exe + +You will get + + git-annex: ssh: createProcess: does not exist (No such file or directory) + failed + git-annex: drop: 1 failed + +### What version of git-annex are you using? On what operating system? + +Windows 8, + + $ git annex version + git-annex version: 5.20140411-gda795e0 + build flags: Assistant Webapp Webapp-secure Pairing Testsuite S3 WebDAV DNS Feeds Quvi TDFA CryptoHash + key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SKEIN256E SKEIN512E SHA256 SHA1 SHA512 SHA224 SHA384 SKEIN256 SKEIN512 WORM URL + remote types: git gcrypt S3 bup directory rsync web webdav tahoe glacier hook external + local repository version: 5 + supported repository version: 5 + upgrade supported from repository versions: 2 3 4 + + +### Please provide any additional information below. + + diff --git a/doc/todo/git-annex_ignores_GIT__95__SSH/comment_1_958dd21d7e981232f03b4516521ac226._comment b/doc/todo/git-annex_ignores_GIT__95__SSH/comment_1_958dd21d7e981232f03b4516521ac226._comment new file mode 100644 index 000000000..c13c3d089 --- /dev/null +++ b/doc/todo/git-annex_ignores_GIT__95__SSH/comment_1_958dd21d7e981232f03b4516521ac226._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="108.236.230.124" + subject="comment 1" + date="2014-05-16T16:42:41Z" + content=""" +This is good spotting of a git configuration that git-annex does not support. + +However, I doubt that even if I made it use `GIT_SSH`, it would be useful. git-annex uses several features that are probably unique to openssh, including connection caching. While you could disable annex.sshcaching and perhaps get a different ssh to work, it would be much slower. +"""]] diff --git a/doc/todo/git-annex_ignores_GIT__95__SSH/comment_2_319a7e8122e7bc25d9399ba463a16158._comment b/doc/todo/git-annex_ignores_GIT__95__SSH/comment_2_319a7e8122e7bc25d9399ba463a16158._comment new file mode 100644 index 000000000..1294196ba --- /dev/null +++ b/doc/todo/git-annex_ignores_GIT__95__SSH/comment_2_319a7e8122e7bc25d9399ba463a16158._comment @@ -0,0 +1,22 @@ +[[!comment format=mdwn + username="divB" + ip="171.67.172.81" + subject="comment 2" + date="2014-05-17T23:58:19Z" + content=""" +Hi Joey, + +Thanks for your answer. In my opinion, this would be an important requirement for various reasons: + +1.) It is very confusing and results in unpredictable errors. I spent days in finding out what caused all the weird stuff that happened. Even if it is not supported, an error message or at least warning should be issued. + +2.) At least in Windows, plink.exe is the quasi-standard SSH client. All SW I am aware of supports at least plink.exe as alternative to openssh (SVN, git, unison, ...). Even within cygwin I often use plink for X11 forwarding etc. If features like SSH caching do not work with that it's totally fine. + +3.) Even for a unix environment, it is critical to be able to use a wrapper (or at least to configure SSH parameters). In my opinion, this should and must work consistently (git, git-annex and rsync). For example what if I have a dedicated public key for a repository and to not want to use %HOME%\.ssh\id_rsa ? +For unison, I use a wrapper my_ssh.cmd which wraps specialized parameters (in particular SSH key, port) with plink.exe to ssh.exe's interface. Similarly, I might be interested in disabling agent functionality and use GSSAPI etc. etc. + +A little bit OT now: I already wondered if and how inefficient git-annex is in this regard. For example, if I sync content, it seems that ssh opens a new connection for each file! (at least each file results in a signing request in my agent). This happens even if I use ssh.exe. Is there anything wrong? + +Thanks + +"""]] |