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

Re: Issue with sparse checkout

From
MGMartin Gregory <martin.gregory@adelaideinterim.com.au>
Date
Sep 16, 2013, 22:46 UTC
Message-ID
<loom.20130917T004445-713@post.gmane.org>
In-Reply-To
<SDZPSjFXUiRJMCkwPVQvMjk3OTAwMzE@IBMLT4>
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 
?
Regards,
Martin
Previous: Martin GregoryNext: Duy Nguyen
Message 2 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.