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

[Arne Babenhauserheide]

Am Montag 29 Dezember 2008 21:11:49 schrieb Brendan Cully:
> > - 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).

I think I now found one reason: hg export can stumble over merge revisions. 

Best wishes, 
Arne

PS: Alexandre, the DVCS PEP champion for Mercurial, is open for improvement 
suggestions. 
-- 
-- My stuff: http://draketo.de - stories, songs, poems, programs and stuff :)
-- Infinite Hands: http://infinite-hands.draketo.de - singing a part of the 
history of free software.
-- Ein Würfel System: http://1w6.org - einfach saubere (Rollenspiel-) Regeln.

-- PGP/GnuPG: http://draketo.de/inhalt/ich/pubkey.txt
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part.
Url : http://selenic.com/pipermail/mercurial/attachments/20081229/f842a20e/attachment.pgp