hg export usage: Why not default = changes to remote?

[Paul Moore]

2008/12/29 Arne Babenhauserheide <arne_bab at web.de>:
> Hi,
>
> Why doesn't hg export without revisions default to exporting the changes to
> the remote repository?

Hmm, I'm not sure it makes sense, in the general case. What if you
cloned, made some changes, pulled, merged, made some more changes. Is
it possible in that situation to define what the above means,
precisely? I'm sorry, but I don't have time right now to test.

Having said that, would an extension which added a revisionspec
corresponding to this (something like the Bazaar "submit:" revision
used in the corresponding Bazaar script) be possible or useful?

Paul.