Problems pushing local code repository to mercurial project on Google Code?

If you are trying to push back a repository that you cloned, try hg push otherwise try hg push https://blahblah.googlecode. Com/hg For future reference, here's the usage information from Mercurial's built-in help system: $ hg help clone hg clone OPTION... SOURCE DEST $ hg help push hg push -f -r REV... -e CMD --remotecmd CMD DEST I think the reason hg push is failing is because you're giving it too many arguments.

If you are trying to push back a repository that you cloned, try hg push otherwise try hg push https://blahblah.googlecode. Com/hg/ For future reference, here's the usage information from Mercurial's built-in help system: $ hg help clone hg clone OPTION... SOURCE DEST $ hg help push hg push -f -r REV... -e CMD --remotecmd CMD DEST I think the reason hg push is failing is because you're giving it too many arguments.

1 He's not trying to push back one he cloned. He's trying to push a repo he created locally. – Ry4an Sep 9 '09 at 4:51.

Try the 'force'. Force says "and you're allowed to create new remote heads". You google code has no changesets, so no heads, so you're going from zero to one.

I still wouldn't expect that 'force' is required, but it's definitely worth the try. Most people starting a repo from scratch would have cloned the empty repo from google (or bitbucket) first, and then made their changes, and then pushed. I think this is what las3rjock thought you did.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.