mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

move to todo

Browse source
This commit is contained in:
Joey Hess 2013-06-12 15:25:55 -04:00
parent 16942dffae
commit bbd551d0ed
5 changed files with 1 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

8
doc/bugs/Move_ssh_config_to___126____47__ssh__47__git-annex__47__config.mdwn
View file

@ -1,8 +0,0 @@
### Please describe the problem.
Instead of storing config for each remote in ~/.ssh/config, which mixes the user own config with that of git-annex-assistant, which is irritating if (like me) you store your ssh config in a vcs. Since the option -F allows the choice of the config file, it should be possible to move the config into ~/.ssh/git-annex/config. The only issue I see is according to the ssh man page on my system states that the system-wide config is ignored if a config file is specified on the command line.
### What version of git-annex are you using? On what operating system?
I'm using git-annex 4.20130601 on a Debian Testing/Unstable/Experimental mix.

10
doc/bugs/Move_ssh_config_to___126____47__ssh__47__git-annex__47__config/comment_1_284c806e83a32af81b02aea7c7bc285a._comment
View file

@ -1,10 +0,0 @@
[[!comment format=mdwn
username="http://joeyh.name/"
nickname="joey"
subject="comment 1"
date="2013-06-11T14:44:47Z"
content="""
The only interface git provides to do this is `GIT_SSH`, which would have to be set to a wrapper script that runs ssh with the desirned options.
And if that were used, `git pull` by itself would not work on the repositories set up by the assistant. I don't consider that very nice.
"""]]

10
doc/bugs/Move_ssh_config_to___126____47__ssh__47__git-annex__47__config/comment_2_1f55ad6b39906458779b2d604b003ffe._comment
View file

@ -1,10 +0,0 @@
[[!comment format=mdwn
username="http://joeyh.name/"
nickname="joey"
subject="comment 2"
date="2013-06-11T14:48:01Z"
content="""
Also, if you're going to set up something like local pairing, why would you *not* want to commit that config to git along with your other ssh configs? Config files in $HOME are quite frequently edited by helper programs to configure changes, and I personally commit those changes all the time.
Perhaps your real problem is that you have one `.ssh/config` that is shared between multiple hosts, and the git-annex settings are specific to a single host. Have you considered using [vcsh](https://github.com/RichiH/vcsh)?
"""]]

8
doc/bugs/Move_ssh_config_to___126____47__ssh__47__git-annex__47__config/comment_3_b00dce2374aac6968317d05d23bcfaf7._comment
View file

@ -1,8 +0,0 @@
[[!comment format=mdwn
username="https://www.google.com/accounts/o8/id?id=AItOawk3Wgg0XiqYFwM_Pw1RxZwlpNFi65g17sM"
nickname="James"
subject="comment 3"
date="2013-06-12T01:12:24Z"
content="""
Ah, ok, I presumed there was an option in git to set a per-repository ssh command. I've looked at vcsh, but I'm not that confident with git remotes, so I don't use it (I use hg). If a per-repository ssh command added to git, would you consider adding this?
"""]]

10
doc/bugs/Move_ssh_config_to___126____47__ssh__47__git-annex__47__config/comment_4_743d0b077110c5cac1e2f47187b75333._comment
View file

@ -1,10 +0,0 @@
[[!comment format=mdwn
username="http://joeyh.name/"
nickname="joey"
subject="comment 4"
date="2013-06-12T19:23:50Z"
content="""
If it were sane, I'd probably use it.
In the meantime, I'm moving this to [[todo]].
"""]]