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

[Brendan Cully]

On Monday, 29 December 2008 at 20:30, Arne Babenhauserheide wrote:
> Hi, 
> 
> Why doesn't hg export without revisions default to exporting the changes to 
> the remote repository? 
> 
> (I just saw that the workflow in the Python DVCS PEP requires one more step 
> than the one in git and I couldn't find a reason for that - normally people 
> will call outgoing and then select all changes for export
> - Python DVCS PEP: http://docs.google.com/View?docid=dg7fctr4_40dvjkdg64
> ). 

It ought to be pretty easy to add an --outgoing <repo> flag to
export. Note that hg email already has a -o flag to do exactly
this, and the rdiff extension provides a workflow very similar to the
git example. (The git example folds all changes into one patch,
whereas the others preserve local history).