On Sat, Apr 11, 2009 at 02:02:57PM -0400, Caleb Cushing wrote:
> On Sat, Apr 11, 2009 at 1:27 PM, Robin H. Johnson <firstname.lastname@example.org> wrote:
> > hat's explicitly why I mentioned the project above actually. Because
> > one of their objects IS to allow commits into a shallow/narrow checkout.
> I don't care about 'shallow checkout' I need shallow updates... when I
> do a fetch only get me the stuff I need to update my checkout. when I
> think shallow checkout I think only checking out a select subset of
> items, which is again already possible.
That's narrow, not shallow.
Per upstream Git's conventions:
- History is the depth dimension.
- Directories are the width dimension.
And thus 'shallow' means to exclude some history, while narrow means to
only have part of the files in the tree. Sparse is an extension of this,
to have only some subset of files in a single directory, but not the
Narrow is already possible in both CVS and SVN, but it is not natively
in Git, which is the reason that it's been a TODO item for them (you can
get it with the git-cvsserver already, but they want it natively), and
that I mentioned the GSoC project on their side.
Robin Hugh Johnson
Gentoo Linux Developer & Infra Guy
E-Mail : email@example.com
GnuPG FP : 11AC BA4F 4778 E3F6 E4ED F38E B27B 944E 3488 4E85