Right, as Ali said, you should be having your svn (or mercurial) client cache your password; that's the norm, just like you have an agent to cache your ssh password.
Unlike Sourceforge, Google's infrastructure isn't just a "bunch of machines you can ssh into" -- we have a very proprietary hardware/software stack. The chance of allowing users' to install ssh keys is zero. (The closest we've come to such things is AppEngine, where users can run code in our datacenters, but only within an extremely abstracted and jailed sandbox.) On Thu, Dec 23, 2010 at 4:25 PM, Paul <[email protected]> wrote: > You guys should allow users to submit a public key in order to do svn > +ssh. I just started a project, but I'm note sure I'm going to keep it > at google code because I don't really want to go to the webpage to get > my password every time I need to do a commit or update > > What are other folks doing about this? > > thanks, > Paul > > -- > You received this message because you are subscribed to the Google Groups > "Project Hosting on Google Code" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<google-code-hosting%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/google-code-hosting?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Project Hosting on Google Code" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-code-hosting?hl=en.
