{"thread":{"id":"34939","subject":"Issue with sparse checkout","startedAt":"2013-09-16T13:20:28Z","lastAt":"2013-09-17T22:16:22Z","messageCount":4,"participants":["Martin Gregory","Duy Nguyen"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"227710","messageId":"SDZPSjFXUiRJMCkwPVQvMjk3OTAwMzE@IBMLT4","threadId":"34939","inReplyTo":null,"subject":"Issue with sparse checkout","fromName":"Martin Gregory","fromEmail":"marting@adelaideinterim.com.au","sentAt":"2013-09-16T13:20:28Z","receivedAt":"2013-09-16T13:20:28Z","isPatch":false,"sender":{"key":"marting@adelaideinterim.com.au","avatar":null},"body":"I wonder if you can advise me if this is a bug with sparsecheckout, or if not what I'm doing wrong:\n\nhttp://pastebin.com/HUaWrtef\n\nBasically, I believe that when I do git read-tree, I should be left with only\nthe directory CONFIGURATION.\n\nHowever, DV_TDM remains.   But it's status seems to be \"indeterminate\" from\ngit's point of view - it neither reports it as being an untracked nor as being\ndeleted when I delete it.   FWIW, that directory contains a folder which\ncontains files.\n\nI also tried a simpler sparsecheckout file, with just\n/CONFIGURATION\n\nin it, but this was worse: it left DV_SERVICES in place as well.\n\nThanks for any advice.\n\nThis is git 1.8.3.msysgit.0\n\nMartin\n"},{"id":"227723","messageId":"loom.20130917T004445-713@post.gmane.org","threadId":"34939","inReplyTo":"SDZPSjFXUiRJMCkwPVQvMjk3OTAwMzE@IBMLT4","subject":"Re: Issue with sparse checkout","fromName":"Martin Gregory","fromEmail":"martin.gregory@adelaideinterim.com.au","sentAt":"2013-09-16T22:46:03Z","receivedAt":"2013-09-16T22:46:03Z","isPatch":false,"sender":{"key":"martin.gregory@adelaideinterim.com.au","avatar":null},"body":"An additional note.  I did \n\ngit ls-files -v | grep ^S \n\nand I can see that the files that remain in the working version have the ^S \nbit set. \n\nSo it does feel like a bug to me: why are files with ^S set remaining in the \nworking version after \n\ngit read-tree -mu HEAD \n\n?\n\nRegards,\n\nMartin\n"},{"id":"227744","messageId":"CACsJy8A5hxr-oSiLTmY2iA-LrmnCk3PW9SxLcvYdJgfDV7Qppg@mail.gmail.com","threadId":"34939","inReplyTo":"loom.20130917T004445-713@post.gmane.org","subject":"Re: Issue with sparse checkout","fromName":"Duy Nguyen","fromEmail":"pclouds@gmail.com","sentAt":"2013-09-17T11:27:05Z","receivedAt":"2013-09-17T11:27:05Z","isPatch":false,"sender":{"key":"pclouds@gmail.com","avatar":"https://avatars.githubusercontent.com/u/720?v=4"},"body":"On Tue, Sep 17, 2013 at 5:46 AM, Martin Gregory\n<martin.gregory@adelaideinterim.com.au> wrote:\n> An additional note.  I did\n>\n> git ls-files -v | grep ^S\n>\n> and I can see that the files that remain in the working version have the ^S\n> bit set.\n>\n> So it does feel like a bug to me: why are files with ^S set remaining in the\n> working version after\n>\n> git read-tree -mu HEAD\n>\n> ?\n\nI don't know. Maybe the bits are set, but then the remove operation\nfails (silently). I tried to reproduce on Linux without success. It\nseemed to work ok. Can you copy the (stripped down if necessary)\nrepository somewhere? Pack the whole thing including worktree and\nconfig file, just in case.\n-- \nDuy\n"},{"id":"227809","messageId":"SDZTMVc5MiUjTUpfPVQvNzQwODk1NjI@IBMLT4","threadId":"34939","inReplyTo":"CACsJy8A5hxr-oSiLTmY2iA-LrmnCk3PW9SxLcvYdJgfDV7Qppg@mail.gmail.com","subject":"re[2]: Issue with sparse checkout","fromName":"Martin Gregory","fromEmail":"marting@adelaideinterim.com.au","sentAt":"2013-09-17T22:16:22Z","receivedAt":"2013-09-17T22:16:22Z","isPatch":false,"sender":{"key":"marting@adelaideinterim.com.au","avatar":null},"body":"Hi Duy,\n\nThanks for taking a look.\n\n>>  > So it does feel like a bug to me: why are files with ^S set remaining in\n>>  the\n>>  > working version after\n>>  >\n>>  > git read-tree -mu HEAD\n>>  >\n>>  > ?\n>>\n>>  I don't know. Maybe the bits are set, but then the remove operation\n>>  fails (silently). I tried to reproduce on Linux without success.\n\nI also tried to make a small repo to reproduce and failed.\n\nI will try to strip and send ... might take a little while to get to the\npoint where it still happens but there's no work related stuff in there\n\nThanks again,\n\nMartin\n"}]}