RE: clarify git clone --local --shared --reference

From: Loeliger Jon-LOELIGER <jdl@freescale.com>
Date: Jun 8, 2007, 15:57 UTC
Message-ID: <AF0367BA48C55940A43CCF08DF35553C013C76BF@az33exm24.fsl.freescale.net>
In-Reply-To: <20070608053750.GB18521@spearce.org>

Shawn O. Pearce wrote:

Show 12 quoted lines

> 
> Brandon Casey <casey@nrlssc.navy.mil> wrote:
> > ok. I just want to make sure this is not really about prune'ing.
> > 
> > In the following, source and --shared repos are identical except...
> > 1) Source repo contains loose objects which are new commits.
> >    --shared repo does git-pull.
> >    we fast-forward, copying very little.
> >    success.
> 
> Copying nothing actually.  All of the objects required are in the
> source repository, so --shared needs nothing additional.

So the thing I find myself wanting to do is A "crib from local copy". That is, the network Cost is large, so when cloning point to a local (ie, already on same Filesystem) clone that is Similar, use it as a reference, but, in the end, Create a complete copy into the new repository.

I don't want it hard linked with --local. I don't want it shared with --shared. I don't want it as an altrnate source with --reference.

What I want is a new, clean, complete, unshared repository.

But for efficiency reasons, I want to grab objects From a different, filesystem-local clone if possible.

Does that work?

jdl