guberm / tortoisegit

Automatically exported from code.google.com/p/tortoisegit
0 stars 0 forks source link

ssh key not used for new remote after clone #2492

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Clone a repository through ssh, select your ssh key, enter a different name 
for the remote
2. 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 1.8.14.0 (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.

Original issue reported on code.google.com by yves.goe...@gmail.com on 23 Apr 2015 at 10:52