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

Re: Behavior change in 2.7.0: With core.sparseCheckout some files have the skip-worktree bit set after a checkout.

From
Duy Nguyen <pclouds@gmail.com>
Date
Jan 8, 2016, 10:49 UTC
Message-ID
<CACsJy8A7LR0xmwuqCKxxiiGeApywYb+_Zxcp=PG=sHHfpeBZRg@mail.gmail.com>
In-Reply-To
<trinity-5caa2985-5cf1-453b-9a9e-bcce057f8615-1452249323061@3capp-gmx-bs51>
On Fri, Jan 8, 2016 at 5:35 PM, Micha Wiedenmann <mw-u2@gmx.de> wrote:
> Hi,
>
> I want to report a change in behavior Git 2.7.0. With `core.sparseCheckout` set to true, `git checkout` results in some files with a set skip-worktree bit, which was not the case in 2.6.4. (I am using Git for Windows, but assume this is a Git issue, which is why I report it to this list.)

I might know the reason (and I'm quickly becoming king of regressions). Checking...

-- 
Duy
Previous: Micha Wiedenmann
Message 2 of 2 in “Behavior change in 2.7.0: With core.sparseCheckout some files have the skip-worktree bit set after a checkout.”
  1. Micha WiedenmannJan 8, 2016
  2. Duy NguyenJan 8, 2016

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.