git commits to Systemtap

[Dave Nomura]

One other piece possible important piece is that the my username on the 
machine where I am doing the commit is different than the redhat 
username when I requested git write permission.

Dave Nomura wrote:
> I got as far as the "git push" and got the following:
> vervainp2.rchland.ibm.com% git push
> fatal: The remote end hung up unexpectedly
> vervainp2.rchland.ibm.com% git pull
> Already up-to-date.
> vervainp2.rchland.ibm.com% git push
> fatal: The remote end hung up unexpectedly
>
> I originally got the clone via:
>    git clone git://sources.redhat.com/git/systemtap.git git
>
> Do I need to use the "ssh:" variant to create the clone?  Is there any
> sort of publickey stuff that I need to set up before using the ssh:
> variant?   Here's what I got when I tried the ssh: variant:
> vervainp2.rchland.ibm.com% git clone
> ssh://sources.redhat.com/git/systemtap.git systap
> Initialize systap/.git
> Initialized empty Git repository in /home/dcn/systemtap/systap/.git/
> The authenticity of host 'sources.redhat.com (209.132.176.174)' can't be
> established.
> RSA key fingerprint is 1d:1e:46:7f:4d:73:8d:10:20:c3:4c:5a:34:14:44:23.
> Are you sure you want to continue connecting (yes/no)? yes
> Warning: Permanently added 'sources.redhat.com,209.132.176.174' (RSA) to
> the list of known hosts.
> Permission denied (publickey,gssapi-with-mic).
> fatal: The remote end hung up unexpectedly
>
>
>
> David Smith wrote:
>>
>> 4: Step 3 checked your changes in locally.  Now we need to push them
>> back to the server so that others can see your changes.
>>
>> # git push
>>
>> It is possible that the push will fail at this point, which means that
>> someone else has made a change since you did your clone.  In this case,
>> you'll need to to update your local repository (and resolve any merge
>> conflicts), like this (corresponds to "cvs update"):
>>
>> # git pull
>>
>> Once the pull succeeds, try the "git push" again.
>>
>> Hopefully I've covered the basics here.
>>
>>   
>
>
>