{"thread":{"id":"31864","subject":"Unexpected directories from read-tree","startedAt":"2012-10-18T23:10:38Z","lastAt":"2012-10-19T16:10:12Z","messageCount":3,"participants":["Uri Moszkowicz","Nguyen Thai Ngoc Duy"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"201537","messageId":"CAMJd5AQhcvWVwsZHPknAXvNpqnfqdCtx-xUv39Au1=x-1_ExMg@mail.gmail.com","threadId":"31864","inReplyTo":null,"subject":"Unexpected directories from read-tree","fromName":"Uri Moszkowicz","fromEmail":"uri@4refs.com","sentAt":"2012-10-18T23:10:38Z","receivedAt":"2012-10-18T23:10:38Z","isPatch":false,"sender":{"key":"uri@4refs.com","avatar":null},"body":"I'm testing out the sparse checkout feature of Git on my large (14GB)\nrepository and am running into a problem. When I add \"dir1/\" to\nsparse-checkout and then run \"git read-tree -mu HEAD\" I see dir1 as\nexpected. But when I add \"dir2/\" to sparse-checkout and read-tree\nagain I see dir2 and dir3 appear and they're not nested. If I replace\n\"dir2/\" with \"dir3/\" in the sparse-checkout file, then I see dir1 and\ndir3 but not dir2 as expected again. How can I debug this problem?\n"},{"id":"201544","messageId":"CACsJy8BeMPwRtU9LQ9aS=0NY7vo_hXQs5Vxo9krXb+epqf=Fdw@mail.gmail.com","threadId":"31864","inReplyTo":"CAMJd5AQhcvWVwsZHPknAXvNpqnfqdCtx-xUv39Au1=x-1_ExMg@mail.gmail.com","subject":"Re: Unexpected directories from read-tree","fromName":"Nguyen Thai Ngoc Duy","fromEmail":"pclouds@gmail.com","sentAt":"2012-10-19T03:34:27Z","receivedAt":"2012-10-19T03:34:27Z","isPatch":false,"sender":{"key":"pclouds@gmail.com","avatar":"https://avatars.githubusercontent.com/u/720?v=4"},"body":"On Fri, Oct 19, 2012 at 6:10 AM, Uri Moszkowicz <uri@4refs.com> wrote:\n> I'm testing out the sparse checkout feature of Git on my large (14GB)\n> repository and am running into a problem. When I add \"dir1/\" to\n> sparse-checkout and then run \"git read-tree -mu HEAD\" I see dir1 as\n> expected. But when I add \"dir2/\" to sparse-checkout and read-tree\n> again I see dir2 and dir3 appear and they're not nested. If I replace\n> \"dir2/\" with \"dir3/\" in the sparse-checkout file, then I see dir1 and\n> dir3 but not dir2 as expected again. How can I debug this problem?\n\nPosting here is step 1. What version are you using? You can look at\nunpack-trees.c The function that does the check is excluded_from_list.\nYou should check \"ls-files -t\", see if CE_SKIP_WORKTREE is set\ncorrectly for all dir1/*, dir2/* and dir3/*. Can you recreate a\nminimal test case for the problem?\n-- \nDuy\n"},{"id":"201557","messageId":"CAMJd5ATF7LzhnpEpcoHcimsmgbYUVrXHwUnrURSJiBtQA8a68A@mail.gmail.com","threadId":"31864","inReplyTo":"CACsJy8BeMPwRtU9LQ9aS=0NY7vo_hXQs5Vxo9krXb+epqf=Fdw@mail.gmail.com","subject":"Re: Unexpected directories from read-tree","fromName":"Uri Moszkowicz","fromEmail":"uri@4refs.com","sentAt":"2012-10-19T16:10:12Z","receivedAt":"2012-10-19T16:10:12Z","isPatch":false,"sender":{"key":"uri@4refs.com","avatar":null},"body":"I am using 1.8.0-rc2 but also tried 1.7.8.4. Thanks for the suggestion\nto use \"ls-files -t\" - that's exactly what I was looking for. With\nthat I was easily able to tell what the problem is: missing \"/\" from\nthe sparse-checkout file.\n\nOn Thu, Oct 18, 2012 at 10:34 PM, Nguyen Thai Ngoc Duy\n<pclouds@gmail.com> wrote:\n> On Fri, Oct 19, 2012 at 6:10 AM, Uri Moszkowicz <uri@4refs.com> wrote:\n>> I'm testing out the sparse checkout feature of Git on my large (14GB)\n>> repository and am running into a problem. When I add \"dir1/\" to\n>> sparse-checkout and then run \"git read-tree -mu HEAD\" I see dir1 as\n>> expected. But when I add \"dir2/\" to sparse-checkout and read-tree\n>> again I see dir2 and dir3 appear and they're not nested. If I replace\n>> \"dir2/\" with \"dir3/\" in the sparse-checkout file, then I see dir1 and\n>> dir3 but not dir2 as expected again. How can I debug this problem?\n>\n> Posting here is step 1. What version are you using? You can look at\n> unpack-trees.c The function that does the check is excluded_from_list.\n> You should check \"ls-files -t\", see if CE_SKIP_WORKTREE is set\n> correctly for all dir1/*, dir2/* and dir3/*. Can you recreate a\n> minimal test case for the problem?\n> --\n> Duy\n"}]}