![]() I gladly pay for tools but I need to see the value and sourcetree does more and has no cost so I just couldn't continue with git-tower. Although things are a little more hidden in the UI for stuff that was upfront in git-tower, all the functionality I needed was there. Before committing I noticed sourcetree had a bunch of updates including a major one that seriously boosted performance on my large projects and the bug on appending was fixed. I would have paid the $79 to buy it but that was in USA dollars and I felt that was too high in my currency when developers in my country generally make 1/2 of developers in the USA. git-tower was fast and was a little easier to use (for example automatic stashing) and things in the UI were worded a little more intuitively. I was just too frustrated this time so I moved to a trial of git-tower. ![]() A short while ago it got really slow and it would mess things up just trying to do a simple append to the last commit (on a project where I am the only person submitting). However it was still very useable when it was slow except on my largest projects but I could fall back to the command line if needed. ppk format private key to a standard PEM format private key: puttygen privatekey.ppk -O private-openssh -o privatekey.pem. Then, use the following command to convert the. This will also install the command-line version of puttygen, the PuTTY key generator tool. Sourcetree seems to have a history of working great, getting an update and then performing really slow until another update. First, install PuTTY for Mac using brew install putty or port install putty (see below). For basic things the command line is fine but I'm finding more and more I like the visual representation of what has changed offered in sourcetree and git-tower. Jason's Experience Used command line, git-tower and sourcetree.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |