git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: sparse checkout - weird behavior

From
PHPaul Hammant <paul@hammant.org>
Date
Jan 26, 2017, 11:20 UTC
Message-ID
<CA+298UhHyXvHZzuuVAz-KYuPJydKY4JksKyBPe+VjsL+zOn74Q@mail.gmail.com>
In-Reply-To
<20170126045936.wyleenuwunhrvbn2@sigill.intra.peff.net>
Well I feel a bit silly. Thanks for responding.
On Wed, Jan 25, 2017 at 11:59 PM, Jeff King <peff@peff.net> wrote:
Show 29 quoted lines
> On Wed, Jan 25, 2017 at 10:21:19PM -0500, Paul Hammant wrote:
>
>> Related bug (maybe the same). Reproduction:
>>
>>   $ git clone git@github.com:jekyll/jekyll.git --no-checkout
>>   Cloning into 'jekyll'...
>>   remote: Counting objects: 41331, done.
>>   remote: Compressing objects: 100% (5/5), done.
>>   remote: Total 41331 (delta 0), reused 0 (delta 0), pack-reused 41326
>>   Receiving objects: 100% (41331/41331), 11.91 MiB | 9.15 MiB/s, done.
>>   Resolving deltas: 100% (26530/26530), done.
>>   $ cd jekyll
>>   $ git config core.sparsecheckout true
>>   $ echo 'CONDUCT.markdown' > .git/info/sparse-checkout
>>   $ echo 'Gemfile' >> .git/info/sparse-checkout
>>   $ echo 'Rakefile' >> .git/info/sparse-checkout
>>   $ echo 'appveyor.yml' >> .git/info/sparse-checkout
>>   $ git checkout --
>>   Your branch is up-to-date with 'origin/master'.
>>   $ ls
>>   CONDUCT.markdown Gemfile Rakefile appveyor.yml lib
>>
>> I was not expecting to see 'lib' in the resulting file list
>
> Yep, I think this is the same problem. Inside lib, you get only
> "lib/theme_template/Gemfile", because it matches your unanchored
> pattern. Using "/Gemfile" in the sparse-checkout file fixes it.
>
> -Peff
Previous: Jeff King
Message 3 of 3 in “Re: sparse checkout - weird behavior”
  1. Paul HammantJan 26, 2017
  2. Jeff KingJan 26, 2017
  3. Paul HammantJan 26, 2017

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.