Clonning only from version and diff before pulls

Mark Williamson mark.williamson at cl.cam.ac.uk
Thu Aug 18 09:34:02 CDT 2005


> Does Hg do the hardlinks automagically for me, or is there something
> that the user must do to tell it to do so?

If hardlinks can be done (i.e. your repositories on the same filesystem and it 
supports hard links) then it'll do them.  This means storing the file history 
won't take any extra space, although if you have a checked-out working copy 
that will.

There's no special message, it'll just do them.

Cheers,
Mark

> On 8/17/05, Matt Mackall <mpm at selenic.com> wrote:
> > On Wed, Aug 17, 2005 at 04:45:53PM -0400, Daniel Santa Cruz wrote:
> > > > > One of the features of Hg is cloning by hardlinking. If your
> > > > > upstream is on the
> > > > > same filesystem as your working copy, you only use space for your
> > > > > actual current working copy, and the .hg/ files that have been
> > > > > changed by local commits.
> > >
> > > Call me hard-headed, but I'm having a hard time figuring out how to do
> > > this clone operation so that my new repo is still a hg repo, but only
> > > with the tip on it... help... please :)
> >
> > You don't. Every repo is completely self-sufficient and
> > self-contained. There is no main repository.
> >
> > The question is, why would you want to? If the answer is "to save
> > space", hardlinked clones are already space-efficient.
> >
> > --
> > Mathematics is the supreme nostalgia of our time.
>
> _______________________________________________
> Mercurial mailing list
> Mercurial at selenic.com
> http://selenic.com/mailman/listinfo/mercurial


More information about the Mercurial mailing list