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

Re: Issue with sparse checkout

From
Duy Nguyen <pclouds@gmail.com>
Date
Sep 17, 2013, 11:27 UTC
Message-ID
<CACsJy8A5hxr-oSiLTmY2iA-LrmnCk3PW9SxLcvYdJgfDV7Qppg@mail.gmail.com>
In-Reply-To
<loom.20130917T004445-713@post.gmane.org>

On Tue, Sep 17, 2013 at 5:46 AM, Martin Gregory <martin.gregory@adelaideinterim.com.au> wrote:

Show 13 quoted lines
> An additional note.  I did
>
> git ls-files -v | grep ^S
>
> and I can see that the files that remain in the working version have the ^S
> bit set.
>
> So it does feel like a bug to me: why are files with ^S set remaining in the
> working version after
>
> git read-tree -mu HEAD
>
> ?

I don't know. Maybe the bits are set, but then the remove operation fails (silently). I tried to reproduce on Linux without success. It seemed to work ok. Can you copy the (stripped down if necessary) repository somewhere? Pack the whole thing including worktree and config file, just in case.

-- 
Duy
Previous: Martin GregoryNext: Martin Gregory
Message 3 of 4 in “Issue with sparse checkout”
  1. Martin GregorySep 16, 2013
  2. Martin GregorySep 16, 2013
  3. Duy NguyenSep 17, 2013
  4. re[2]: Issue with sparse checkoutMartin Gregory, Sep 17, 2013

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.