From: Joshua Jensen <jjensen@workspacewhiz.com>
To: Jay Soffian <jaysoffian@gmail.com>
Cc: git <git@vger.kernel.org>
Subject: Re: sparse checkout bug?
Date: Sat, 24 Sep 2011 14:19:18 -0600 [thread overview]
Message-ID: <4E7E3B46.1040002@workspacewhiz.com> (raw)
In-Reply-To: <CAG+J_DwRPq69TUMOeqU5O9pv=cHZWEP1VJ1_NRaJv5BSFhF00g@mail.gmail.com>
----- Original Message -----
From: Jay Soffian
Date: 9/24/2011 1:50 PM
> I wanted to exclude a single massive directory from a checkout (the
> LayoutTests directory from WebKit, which includes 130k files), so I
> tried:
>
> $ git config core.sparsecheckout true
> $ echo '*'> .git/info/sparse-checkout
> $ echo '!LayoutTests'>> .git/info/sparse-checkout
> $ git read-tree -m -u HEAD
>
> But LayoutTests is not being excluded. I also tried every variation of
> including leading/trailing slash and trailing '*'.
>
This bug has very recently been discussed on the mailing list.
As a workaround, use:
/*
instead of:
*
You said you have tried this already, but it works for me. The only
thing I do in addition is this:
/*
!LayoutTests/
-Josh
prev parent reply other threads:[~2011-09-24 20:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-24 19:50 sparse checkout bug? Jay Soffian
2011-09-24 20:19 ` Joshua Jensen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4E7E3B46.1040002@workspacewhiz.com \
--to=jjensen@workspacewhiz.com \
--cc=git@vger.kernel.org \
--cc=jaysoffian@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox