Re: sparse support in pu
- From
Johannes Schindelin <johannes.schindelin@gmx.de>
- Date
- Aug 17, 2009, 13:23 UTC
- Message-ID
- <alpine.DEB.1.00.0908171522510.4991@intel-tinevez-2-302>
- In-Reply-To
- <eaa105840908170552m3eaf0f92j523ddad98dd67a3@mail.gmail.com>
Hi,
On Mon, 17 Aug 2009, Peter Harris wrote:
Show 7 quoted lines
> On Mon, Aug 17, 2009 at 8:29 AM, Johannes Schindelin wrote: > > If I want to have a sparse checkout, I know which files I _want_. > > That's funny. I have a git tree that would benefit from sparse checkout. > I know which path I _don't_ want. Specifying all the paths I want would > be a rather longer (and more error-prone) list. I suspect it would be > best to support both.
Yes, I agree, but the common case is for people to know what they are working on, right?
Show 6 quoted lines
> Does sparse use the same parser as .gitignore? (I guess not, if it > handles trailing slashes differently?) If so, it would be trivial to > turn "exclude path" into "exclude all but path" (or vice-versa) with: > > * > !path
That was the idea behind my suggestion to allow .gitignore syntax. And indeed, that is what happened.
Ciao, Dscho