Thanks, worked as described. Interestingly once you do this you can also:
> hg clone myproj myproj and the full https: path with password ends up in myproj/.hg/hgrc. You can then push to it directly. However, this is a bit dangerous as you then have the password lying around in clear text... -Drew On May 29, 2:50 pm, Ben Collins-Sussman <[email protected]> wrote: > I think you may need to consult the hg book (hgbook.red-bean.com) > about this, but my understanding is that you can create a [paths] > section in your .hgrc file and define shortcuts for pushing. For > example: > > [paths] > myproj = https://username:[email protected]/hg > > ...and then a simple "hg push myproj" will always authenticate for you. > > On Thu, May 28, 2009 at 5:11 PM, Drew <[email protected]> wrote: > > > First, thanks for the mercurial support guys ! > > > On bitbucket I was able to lodge a public key which allowed me to push > > to a ssh: repository, with googlecode I need to use the autogenerated > > password to push to a https: repo. How can I set things up so I don't > > need to enter the password manually all the time ? > > > -Drew --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Hosting at 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 -~----------~----~----~----~------~----~------~--~---
