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

re[2]: Issue with sparse checkout

From
MGMartin Gregory <marting@adelaideinterim.com.au>
Date
Sep 17, 2013, 22:16 UTC
Message-ID
<SDZTMVc5MiUjTUpfPVQvNzQwODk1NjI@IBMLT4>
In-Reply-To
<CACsJy8A5hxr-oSiLTmY2iA-LrmnCk3PW9SxLcvYdJgfDV7Qppg@mail.gmail.com>
Hi Duy,
Thanks for taking a look.
Show 10 quoted lines
>>  > 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.
I also tried to make a small repo to reproduce and failed.

I will try to strip and send ... might take a little while to get to the point where it still happens but there's no work related stuff in there

Thanks again,
Martin
Previous: Duy Nguyen
Message 4 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.