on binary export and import

[Jan Hudec]

On Wed, Sep 07, 2005 at 04:35:49 -0700, TK Soh wrote:
> > What we want is something like:
> > 
> >  hg push -o changes.hg http://remote/hg/
> >  hg pull changes.hg
> > 
> > But I might also want to do:
> > 
> >  hg pull http://remote/changes.hg
> > 
> > This lets people publish all their changes in a static form without
> > publishing a whole repo (at the expense of possibly having to download
> > the whole thing every time)
> 
> Seems like an interesting idea. But again, the push/pull mechanism won't work
> for me, at least when it requires accessing the remote repo. If I had been able
> to use http, this feature wouldn't be necessary. I guess a more refined
> mechanism based on debugchangegroup and addchangegroup will serve better
> purpose.

The difference between
    hg push http://remote/hg/
and
    hg push -o changes.hg http://remote/hg/
is, that the first needs _write_ access to http://remote/hg/, while the
second only needs _read_ access. Which generally makes a huge difference.

Still, if you can't get read access either, you will need some kind of
    hg push -o changes.hg -r abcdef01:tip
or something like that.

--
						 Jan 'Bulb' Hudec <bulb at ucw.cz>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://www.selenic.com/pipermail/mercurial/attachments/20050907/3966c432/attachment.pgp