Instead of SVN, use Git to do version control tortoisegit SSH configuration

From: Http://www.sineysoft.com/blog/catalog.asp?tags=svn+git+tortoisegit+ssh+%E9%85%8D%E7%BD%AE

Previous version management of the project has been using SVN, recently found Git, was immediately attracted by the characteristics of his profile, immediately kicked SVN out of the server, all using Git as a version management tool, first of its clone (SVN check out) speed, And there's not going to be anything like svn in every folder. SVN hidden directories, instead of storing historical data in a compressed file system at the top-level directory, where there is no historical data information at all levels of subdirectories, the catalog looks refreshing and has a much smaller size than svn garbage data.

Finally, the key distributed design, for developers not to commit every commit to the server, but can commit to the local file system, when necessary to push to the server, so that those who can not always keep connected with the server developers (such as writing code at home, Commit, back to the company push to the server), and all local commits can be versioned, ready to roll back to the historical version, so that they resemble a stand-alone version management system and can be rolled back without connecting to the server.

For Windows users, SVN has a very good GUI tool, TORTOISESVN, generally called small turtle, and git also has a small turtle version tortoisegit, also very useful, in the actual use of the process, or a little problem, is about SSH connection, The current tortoisegit use putty as the client of SSH connection, want to configure putty and finally can connect SSH server, it really took a lot of time, in order to facilitate the new tortoisegit users, I simply described the configuration steps as follows:

First enter the Tortoisegit Setting dialog box (right click on any directory to select tortoisegit->setting)

Enter the network page and configure the SSH client as the TortoisePlink.exe in the Tortoisegit/bin directory

Run the bin/directory of the Pageant.exe program, add key to join your SSH privete key file, enter the password, each time you have to start the pageant program and enter the password

Keep the Pageant.exe program running, this time you should be able to use Tortoisegit clone's git code warehouse

such as Ssh://test@192.168.1.100:3220/test.git

If there is a problem, you can replace the TortoisePlink.exe with the official plink.exe (need to download separately)

The good news is that the next version of the Tortoisegit SSH configuration should not be so cumbersome, saying in its official Google code that it already supports open SSH and can automatically eject the password confirmation box