Re: .gitlink for Summer of Code

From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: Mar 25, 2007, 20:54 UTC
Message-ID: <Pine.LNX.4.63.0703252252500.4045@wbgn013.biozentrum.uni-wuerzburg.de>
In-Reply-To: <20070325203901.GB12376@spearce.org>

Hi,

On Sun, 25 Mar 2007, Shawn O. Pearce wrote:

Show 17 quoted lines

> Matthieu Moy <Matthieu.Moy@imag.fr> wrote:
> > Eric Lesh <eclesh@ucla.edu> writes:
> > 
> > > .gitlink is for a lightweight checkout of a branch into a separate
> > > directory on the local filesystem.
> > 
> > I think it's a pitty to restrict yourself to _local_ filesystem. There
> > are tons of cases where you have a fast, non-NFS, access to a machine
> > and would like to host your repository there.
> > 
> > That said, I suppose removing this restriction moves the solution from
> > the category "quick and efficient hack" to something much harder.
> 
> Yes.  But there's another project on the ideas list that addresses
> that (``Lazy Clone'').  It is quite a bit more difficult than the
> .gitlink idea as the implementation requires a network protocol
> client implemented somewhere near the read_sha1_file interface.

Not only that. You'd have to change the way read_sha1_file() is called to allow fetching more than one object at a time. Otherwise this will be so slow as to be unusable.

That's basically the reason why I changed my mind, and preferred shallow clones over lazy clones.

Ciao, Dscho