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