Search code examples
mercurialgoogle-code

Pushing Mercurial changesets from my local clone to "the real" clone?


I created a project at Google code, and am using Mercurial for it.

I made a clone of the project: farm-myclone up on Google code.

I pull out a copy of farm-myclone, and start adding files, modifying files, etc.

I use hg commit, then hg push to get changes back into my clone's repository.

Now I want to move these changes into the real repository, just named farm.

Do I just do something like:

hg push [farm-myclone] to [farm]

so that whatever the state of my clone is gets pushed to the real clone?

Is that right? I'm an SVN user so this is a bit confusing to me.

Thanks


Solution

  • I think you've got one more clone than you actually need: You probably don't need "farm-myclone" to exist at all on Google Code.

    If that main project is just called "farm", then when you run hg clone to make a clone of it, you get a clone on your local machine. This clone is a full Mercurial repository in all respects. When you're ready to publish your changes for the rest of the world to see, use hg push to push them up to the "farm" repository.

    I think the presence of the additional "farm-myclone" repository is confusing the issue.