Live data from Hacker News

GitHub for Windows

github.com

191–200 of 248 posts

Re: GitHub for Windows

#191
post #152

As a developer, I feel obligated to disagree with anything Windows. I'd honestly rather force people to use Linux or OSX than windows. I'd go so far as to say I would totally exclude Windows users entirely and that I support attempts to make it more difficult for a Windows user to use something.

That is why github will beat your social code management site.

Re: GitHub for Windows

#195
post #160
post #111

Earlier quoted context omitted.

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.

It's not about being unfamiliar with the CLI, it's that Windows isn't like OSX/Linux in that you can just store your keys in a .ssh folder and be done with it (at least not if you don't use cygwin/msys) 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 terr…

Putting all of your SSH keys in a .SSH folder (inside your user directory) and setting up OpenSSH to look through those when you try to connect to something is exactly what installing Git on Windows does.

This seems pretty friendly to me. Is there something I'm missing?

Re: GitHub for Windows

#196

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/

s/peace/piece/ - please!!

Re: GitHub for Windows

#197
post #15

This is very interesting. Will this tool be able to work with non-github git repositories?

Yes, you can drag-and-drop any git repo folders in it, and it works. However, it only supports one upstream URL per repository.

Re: GitHub for Windows

#198

Earlier quoted context omitted.

I'm sure you'd love to still be programming in assembly, but some of us prefer to spend our time actually, you know, not mucking around with stuff that is an utter waste of our time.

It takes less than 4 minutes to do. And way to ignore every, other, thing I mention in there, like how something else is probably better suited for your needs if you think it is an "utter waste of time". The level of discourse and use the downvote just amazes me anymore. Seriously, how can you be that much of a douche after I made very basic, undisputed points?

[deleted]

Re: GitHub for Windows

#199

Earlier quoted context omitted.

Nobody said anything about it being scary to type "ssh-keygen -t rsa" but rather about the responsibility that comes with it. I'd bet my right hand the more than 25% of "competent developers" that are "managing servers" will have made security mistakes while storing their ssh keys on a level with storing the password in plaintext on a .txt file on the desktop. Thats whats scary about "crypto stuff", not that it isn't…

Outside of checking id_rsa into your Git repo or emailing it, (which would be equivalent to doing so with passwords.txt), SSH (and thus Git) protect you from leaving id_rsa with open permissions. Though it may not be obvious that id_rsa is something to protect. (though again, I don't go emailing random files I don't understand either). That having been said, I'm certainly not a security expert. Are there other common…

Do I understand right that id_rsa is an equivalent of password.txt in that you have big broblems if someone gets it? In this case I really worry about its being stored in the open in some /users/AppData and not on some TrueCrypt drive that is not mounted by default.

Re: GitHub for Windows

#200
post #110

Earlier quoted context omitted.

"Scary crypto stuff"? So you don't understand how PKI works and you're trying to use distributed source control? (I say this not to be a jerk, but because there aren't exactly a wealth of good alternatives given it is a distributed source control mechanism. PKI comes with the territory and an SSH key generation is part of that) GitHub doesn't take any more setup than a standard Git setup takes (well, outside of signi…

For many people there Github = git, so saying github isn't much harder to set up than Git isn't saying much. Using git on Windows has historically not been super fun. The CLI installer mostly works, but it's pretty clunky. Cygwin works fine too, but it's also not especially elegant. At the very least, known of these solutions conform to the expectations of people of the platform. The GUI clients on Windows last I loo…

> The GUI clients on Windows last I looked (a year ago) were pretty terrible, especially compared to TortoiseSVN, which isn't bad

There is TortoiseGit, which is basically TortoiseSVN over git. It looks much the same.

You can regard it as a good place to start with git, or as something that stops you learning what makes git special.

Post reply on HN