I'm trying to understand how to push my mercurial patches to a remote repo (say, bitbucket.org), without having to apply them first (actually committing them). My motivation is to first have a remote backup to my work before it's final, and also to be able to share these patches with other people or work on them from a different machine.
My normal workflow is this:
$ hg qnew some-feature -m "work on some feature"
... work on some files
$ hg qref
--> bug or other feature request comes along
$ hg qpop some-feature
$ hg qnew new-feature -m "work on different feature"
... work on new stuff
$ hg qref
At the point, I'd like to push my unfinished, uncommitted patches to the repo. I've read about how Mercurial queues are in fact their own repos and can therefore be manipulated just like a normal hg repo, but I'm unclear as to the workflow with respect to what I'm trying to do. I've aliased mq command in my shell to hg -R $(hg root)/.hg/patches, but I'd appreciate some feedback on how people manage remote backup and sharing of uncomitted patches. thanks.
