Subject: Re: [boost] [GitHelp] Sandbox library to GitHub
From: Edward Diener (eldiener_at_[hidden])
Date: 2012-12-27 19:42:59
On 12/27/2012 5:10 PM, Brian Wood wrote:
> Edward Diener:
>> On 12/26/2012 5:10 AM, Daniel Pfeifer wrote:
>>> 2012/12/26 Andrey Semashev <andrey.semashev_at_[hidden]>:
>>>> Perhaps you didn't set up a ssh public key?
>>>> You will also have to add the key to TortoiseGit/PuTTY.
>>> If you push over HTTPS, you don't need an ssh key.
>> That sounds like what I want to do. The whole low-level business of
>> generating public/private keys, when I already have signed up for GitHub
>> with a username/password, seems silly to me. I know the Linux gurus all
>> love this kind of intricate stuff, but I do not.
> It's one command:
> ssh-keygen -t rsa -C "username_at_[hidden]"
What is this command supposed to do ?
I did generate a public/private key pair with something called puttygen
and added the public key on GitHub for my account. I also saved the
private key in a directory locally. I was following the instructions at
http://nathanj.github.com/gitguide/pushing.html. Then I find I am
supposed to do a number of other things and I got lost and disappointed
amid all this complicated stuff.
All of this really seems like overkill. Why should I even bother when
using https and 'git' from the command seems to work just fine.
When I used SVN with TortoiseSVN and used https all I ever had to do was
give my username/password the first time and afterward TortoiseSVN took
care of the rest. I hope I can get TortoiseGit to just do the same
thing. Using a SCCS should be easy and not complicated, even if you have
to issue more complicated commands occasionally.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk