Re: [RFC PATCH 0/9] Narrow/Sparse checkout round 3: "easy mode"

From: James Pickens <jepicken@gmail.com>
Date: Aug 19, 2008, 21:10 UTC
Message-ID: <loom.20080819T210550-149@post.gmane.org>
In-Reply-To: <20080815142439.GA10609@laptop>

Nguyễn Thái Ngọc Duy <pclouds <at> gmail.com> writes:

> From user POV, we can now checkout a single file or a
> subdirectory (checking out subdirectory non-recursively is
> possible too). You may start with a narrow clone like:

Is there any reason for the change in terminology from "sparse" to "narrow"? I understand the difference between "partial" and "sparse", but I can't tell if there's any difference between "narrow" and "sparse". If they are the same thing, then I think "sparse" is the better term.

Show 5 quoted lines

> Last bit. "Narrow rules" for --path|--add-path|--remove-path is
> currently wildcards separated by colons. While it does the job,
> it does not allow to checkout easily a subdirectory
> non-recusively. I was thinking about '*' as "match everything
> except slashes" and '**' as "match everything even slashes".

I like this idea - it would make this much more intuitive to use, since '*' and '**' would work the same as they do in the shell (for shells that support '**' at least). I tried the patch in it's current form, and it took me a while to figure out that paths were non-recursive and '*' was matching everything, including slashes.

James