| Re: [tcf-dev] SVN about to be turn read only |
|
One thing I notice wrong in that wiki page is the instructions for setting up your .ssh authorized_keys. If you haven’t done so already when using SVN, it’s highly recommended when using EGit since EGit has a
bad habit of asking for passwords more than it needs to. At any rate, the suggested method is to create your .ssh directory locally with your public key added to the authorized_keys file and scp it up to build.eclipse.org. The restricted shell will not allow you to
edit these files on the server. Doug. From: tcf-dev-bounces@xxxxxxxxxxx [mailto:tcf-dev-bounces@xxxxxxxxxxx]
On Behalf Of Schaefer, Doug Committer access doesn’t change. It’s all still based on you eclipse.org user id and password. The CDT gang have recorded notes on their experience with a transition. It’s probably a good starting point. http://wiki.eclipse.org/CDT/git Cheers, Doug. From: tcf-dev-bounces@xxxxxxxxxxx [mailto:tcf-dev-bounces@xxxxxxxxxxx]
On Behalf Of Stieber, Uwe Hi Doug, After the conversion, please provide a pointer to a howto describing how to gain back committer access. From what I’ve seen so far at Eclipse.org, it is a bit unclear. Thanks, Uwe J From: tcf-dev-bounces@xxxxxxxxxxx [mailto:tcf-dev-bounces@xxxxxxxxxxx]
On Behalf Of Schaefer, Doug Hey gang, Just a heads up, the SVN repo should be turned read-only any minute. So please hold off check-ins. I went through a practice round yesterday and the conversion should only take a few minutes. I’ll give it a bit of testing, but we should be up and running within a couple of hours. Doug. |