[PATCH 0 of 6] incoming for remote repositories/bundlerepo

[Bryan O'Sullivan]

On Tue, 2006-03-14 at 14:09 +0100, Thomas Arendsen Hein wrote:

> Maybe this makes it too easy to do the wrong thing:
> $ hg incoming http://example.com
> $ hg pull http://example.com
> 
> It seems to simply work, but
> 1. there may be new changesets when doing the pull and
> 2. the bundle has to be created transfered twice.

I think the current behaviour that Benoit has written is good, myself.

> I can imagine allowing --bundle "" or --bundle /dev/null to
> do the same as that longer option above.

But we don't force people to use this when doing incoming on local
repositories - why treat remote ones differently?

> Additionally it would be nice if I can do
> 'hg incoming bundlefile' or 'hg pull bundlefile' in the future.

Yes.

> Or what about 'hg pull --bundle foobar http://example.com',
> symmetric to 'hg push --bundle foobar http://example.com' which
> then could do the same as 'hg unbundle' and 'hg bundle' do now? One
> could then use 'hg incoming foobar' to see what's in the bundle.

+1

	<b