threads / discuss / 28793

sparse checkout using exclusions

Subject: sparse checkout using exclusions

## tl;dr

3 messages between Oct 29, 2011 and Oct 31, 2011.

replies: 2people: 2as markdown or json

Eric Raible· Oct 29, 2011, 00:17 UTC · lore

Hi all.

I was just about to send a long message about using exclusions in sparse-checkout, when I did one last search and saw that all of my problems were fixed by using '/*' instead of '*' as the first line in .git/info/sparse-checkout.

Might it make sense for the example in git-read-tree.html to be updated to include the leading slash?

    /*
    !unwanted

- Eric

Ramkumar Ramachandra· Oct 29, 2011, 05:46 UTC · re: Eric Raible · lore

Re: sparse checkout using exclusions

Hi Eric,

Eric Raible writes:

> Might it make sense for the example in git-read-tree.html to be
> updated to include the leading slash?

This issue was fixed in 5e821231 (git-read-tree.txt: update sparse checkout examples, 2011-09-26).

Cheers.

-- Ram

Eric Raible· Oct 31, 2011, 20:16 UTC · re: Ramkumar Ramachandra · lore

Re: sparse checkout using exclusions

On 10/28/2011 10:46 PM, Ramkumar Ramachandra wrote:

Show 7 quoted lines

> 
> This issue was fixed in 5e821231 (git-read-tree.txt: update sparse
> checkout examples, 2011-09-26).
> 
> Cheers.
> 
> -- Ram

git tag -l --contains => v1.7.8-rc0

I'm running 1.7.7.1.msysgit.0, so I don't have it yet. And neither do any of the online man pages I could find.

But I'm happy that it's fixed. And the commit message is better than what I would have come up with.

Thanks - Eric