{"thread":{"id":"14524","subject":"sparse checkout UI","startedAt":"2008-07-18T13:03:05Z","lastAt":"2008-07-18T13:03:05Z","messageCount":1,"participants":["Nguyen Thai Ngoc Duy"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"83872","messageId":"fcaeb9bf0807180603i23ae3568r80631dafc2888f39@mail.gmail.com","threadId":"14524","inReplyTo":null,"subject":"sparse checkout UI","fromName":"Nguyen Thai Ngoc Duy","fromEmail":"pclouds@gmail.com","sentAt":"2008-07-18T13:03:05Z","receivedAt":"2008-07-18T13:03:05Z","isPatch":false,"sender":{"key":"pclouds@gmail.com","avatar":"https://avatars.githubusercontent.com/u/720?v=4"},"body":"Hi,\n\nI gave up on subtree checkout, the cvs/svn way (making subtree\ntoplevel worktree). Instead I have been working on sparse checkout,\nwhich better fits Git's \"working at toplevel worktree\" philosophy.\nThings are shaping up, but I still have not figured out UI for\nentering/leaving/updating sparse checkout.\n\nShould it be an option for git-checkout, like \"git checkout\n--sparse=git-gui\"? Or making it a separate command? git-clone may need\n\"--sparse-checkout\" option anyway, to be able to do sparse checkout\nfrom the beginning.\n\nOpinions?\n-- \nDuy\n"}]}