151–160 of 248 posts
For those of you looking for a nice Git client for Windows, I suggest checking out TortoiseGit[1]. I can't recommend it enough. It is such a powerful peace of software and I am surprised it is not brought up in discussions more often. http://code.google.com/p/tortoisegit/
Earlier quoted context omitted.
I'm surprised that the responses to this amount to, "I don't understand it, don't want to follow instructions and want a two-click GUI". Git isn't magic. To leverage it well, you need to be willing to get down and dirty with the CLI sooner or later. If you're unwilling to learn Git, don't use it. If you're a dev, source control is one of your tools. Learn it or find a tool that holds your hand more. I don't know how…
You're being down-voted into oblivion. You get even more insulting as you're falling down in your edit. Mm disclaimer: I'm a windows dev by day. I introduced git into that shop I'm working at, the rogue 'I set it up, would you technical guys like to work with it' way. This happened 1.5 years earlier, today it's the blessed and only source control in play (ignoring one sad division having to deal with tfs.. Oh the ago…
Funny how most git users out there (at least according to the git user's survery 2011 [1]) use Linux, yet github seems to go out of its way not to build a tool for its majority of users. I would also go as far as to extrapolate and state that most github users are Linux users (which is true for every programmer I know on github). Would it have been that hard to just use Qt and build a cross platform tool? Or is that…
Earlier quoted context omitted.
You got flamed for that comment because you called generating SSH keys "scary crypto stuff." If that scares you, you probably also enjoy the simplicity of storing passwords in plaintext...
What is your problem with someone being scared of crypto stuff? I find this shows the necessary respect when dealing with security related tasks, since they are HARD. I'm not talking about developing crypto related software, but just setting up a "safe" environment where you can store your SSH Keys in a way that doesn't defeat the purpose of using them in the first place is non-trivial, even for people with degrees.…
SSH is one of the easiest security tools to use safely that has ever existed. I would say it is second in usability only to HTTPS in browsers, while having a much better actual security record, and is infinitely more powerful, while keeping basic operation so simple I once taught my mother to use it.
I am 100% confident that anyone competently engaged in development or systems administration can understand the basic concepts and operations of SSH in five minutes. Any fear of it is irrational. It is not hard, it was specifically designed not to be hard.
I'm equally confident you've not taken the five minutes to understand these relevant concepts, because your statement about setting up a "safe" environment makes no sense in the context of OpenSSH. The defaults are inherently safe, as they should be. You must take specific actions to make the system unsafe.
"GitHub for Windows is a 100% native application"
"The application is written in C#"
Earlier quoted context omitted.
You're being down-voted into oblivion. You get even more insulting as you're falling down in your edit. Mm disclaimer: I'm a windows dev by day. I introduced git into that shop I'm working at, the rogue 'I set it up, would you technical guys like to work with it' way. This happened 1.5 years earlier, today it's the blessed and only source control in play (ignoring one sad division having to deal with tfs.. Oh the ago…
"You want to use Git, you should know how to use Git" If that's insulting, then I'm going to have to learn to live with being a cruel, mean person. Also, it's GitHub's fault that they use an existing secure method of transferring source code instead of writing a new protocol that's easier for you to use. Because 4 step-by-step instructions are too hard to follow. OK. I'm not even asking that you understand it, but si…
They really resent having to learn about other things.
I don't get it. But that's probably why I am employed as a tools engineer... because I like learning.
"GitHub for Windows is a 100% native application" "The application is written in C#" Is managed code the new native?
Was this developed on raw hardware or in a VM running on Linux/Mac?
Great news. I got flamed a month ago [1] for noting how difficult it is to get up and running on GitHub in the Windows world, where things like generating SSH keys aren't exactly part of the daily routine. Glad to hear that they were listening. [1] http://news.ycombinator.com/item?id=3871699
I think it would really help you to have a play with command line Git, just to get a feel for what's going on. SSH keys aren't hard to learn and are useful enough to be worth the time spent. By all means switch to using the GUI after.
The method I chose in Windows was to use pageant (part of Putty) to load the keys. Not sure if I missed this option but you can't autoload keys so when you restart pageant you have to readd the keys (which is not terrible bad, just annoying).
Haven't tried Github For Windows yet but if it fixes the hassle of using ssh keys then I'll probably use it as my main git client for Windows.