ssh key not used for new remote after clone
By yves.goer... on April 23, 2015 10:52 (imported from Google Code)
What steps will reproduce the problem?
- Clone a repository through ssh, select your ssh key, enter a different name for the remote
- Open the settings and select the one remote you just cloned from
What is the expected output? What do you see instead?
The initially used ssh key should be stored in the remote entry. But it's not. This makes any push fail until you manually enter the same ssh key file again.
What version of TortoiseGit and msysgit are you using? On
what operating system?
TortoiseGit 126.96.36.199 (C:\Program Files\TortoiseGit\bin)
git version 1.9.5.msysgit.0 (C:\Program Files (x86)\Git\bin)
Win dows 7 SP1 x64
Please provide any additional information below.
I think this used to work at some time? Not sure. Maybe entering a custom remote name is part of the problem. Since I found that it's possible to rename remotes right away, I always do so. Before, I did that afterwards. I don't like the name "origin" because it doesn't say where that is. Instead I prefer names of the actual server so I can distinguish multiple remote locations.