[vtk-developers] Proposing patches

[TINGAUD Frederic]

Hi all again!

Is the procedure completely up-to-date? Are there steps that demand a manual intervention and that could take some time? Because I followed every step in the wiki, my public key is in Gerrit, but the key is not accepted when I try to connect to vtk.org.
I tried to follow the authentication test (http://www.vtk.org/Wiki/Git/Publish#Authentication_Test)page to no avail:
ssh -vvv git at vtk.org info
OpenSSH_6.1p1, OpenSSL 1.0.1c 10 May 2012
debug2: ssh_connect: needpriv 0
debug1: Connecting to vtk.org [66.194.253.19] port 22.
debug1: Connection established.
debug3: Incorrect RSA1 identifier
debug3: Could not load "/home/ftingaud/.ssh/id_rsa" as a RSA1 public key
debug1: identity file /home/ftingaud/.ssh/id_rsa type 1
debug1: identity file /home/ftingaud/.ssh/id_rsa-cert type -1
debug1: identity file /home/ftingaud/.ssh/id_dsa type -1
debug1: identity file /home/ftingaud/.ssh/id_dsa-cert type -1
debug1: identity file /home/ftingaud/.ssh/id_ecdsa type -1
debug1: identity file /home/ftingaud/.ssh/id_ecdsa-cert type -1
ssh_exchange_identification: Connection closed by remote host

The only part I did not follow in the authentication test is the part about the Kitware password form as it looks like a remaining from the CVS time. But perhaps is it simply why my key is not recognized?

Regards,

Frederic TINGAUD

-----Message d'origine-----
De : David Doria [mailto:daviddoria at gmail.com] 
Envoyé : lundi 8 octobre 2012 19:10
À : TINGAUD Frederic
Cc : vtk-developers at vtk.org
Objet : Re: [vtk-developers] Proposing patches

On Mon, Oct 8, 2012 at 1:04 PM, TINGAUD Frederic <Frederic.TINGAUD at murex.com> wrote:
> Thanks!
> The CVS page clearly states that the git page doesn't exist yet (http://www.vtk.org/Wiki/VTK_Patch_Procedure), so I didn't try to look further for it.
> Fred

I just added a note to the top of that page pointing to the new page.

David
*******************************

This e-mail contains information for the intended recipient only. It may contain proprietary material or confidential information. If you are not the intended recipient you are not authorised to distribute, copy or use this e-mail or any attachment to it. Murex cannot guarantee that it is virus free and accepts no responsibility for any loss or damage arising from its use. If you have received this e-mail in error please notify immediately the sender and delete the original email received, any attachments and all copies from your system.