{"thread":{"id":"27843","subject":"Re: git sparse checkout repo size","startedAt":"2011-07-18T11:29:59Z","lastAt":"2011-07-18T12:25:58Z","messageCount":4,"participants":["gaoyong pan","Nguyen Thai Ngoc Duy"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"171571","messageId":"CALf5Ac2A4XTfkZraVra2sSGJZJ31bTyfmgHZWjptJNgQtXyH7Q@mail.gmail.com","threadId":"27843","inReplyTo":"CALf5Ac223mASO+KGYa3nqB+3eajvRS4QueGT5on6G5kYqhODQQ@mail.gmail.com","subject":"Re: git sparse checkout repo size","fromName":"gaoyong pan","fromEmail":"pan.gaoyong@gmail.com","sentAt":"2011-07-18T11:29:59Z","receivedAt":"2011-07-18T11:29:59Z","isPatch":false,"sender":{"key":"pan.gaoyong@gmail.com","avatar":null},"body":"Hi there,\n\nI use sparse checkout to checkout out two small files(8M total) from a\nlarge repo (~2G), and then check the whole repo size is about 1.2G, it\nreduces about 0.8G repo size, can you tell me how to reduce it much\nmore? I don't want to use submodule or subtree merge because I'd keep\nall the changing history of them in the original repo for the current\nor further logs.\n\n-- \nBest Regards\nLinux user #384184\n@ http://counter.li.org/\n"},{"id":"171572","messageId":"CACsJy8C=LdcaQbc46ssc5=tTXyA-U4N4FAsqjnPyEqwYZuO4LA@mail.gmail.com","threadId":"27843","inReplyTo":"CALf5Ac2A4XTfkZraVra2sSGJZJ31bTyfmgHZWjptJNgQtXyH7Q@mail.gmail.com","subject":"Re: git sparse checkout repo size","fromName":"Nguyen Thai Ngoc Duy","fromEmail":"pclouds@gmail.com","sentAt":"2011-07-18T11:35:08Z","receivedAt":"2011-07-18T11:35:08Z","isPatch":false,"sender":{"key":"pclouds@gmail.com","avatar":"https://avatars.githubusercontent.com/u/720?v=4"},"body":"On Mon, Jul 18, 2011 at 6:29 PM, gaoyong pan <pan.gaoyong@gmail.com> wrote:\n> I use sparse checkout to checkout out two small files(8M total) from a\n> large repo (~2G), and then check the whole repo size is about 1.2G, it\n> reduces about 0.8G repo size, can you tell me how to reduce it much\n> more?\n\nIf history does not really matter to you, use shallow clone. Sparse\ncheckout is more about worktree size, not repo size. The ideal\nsolution would be narrow/sparse clone where you only fetch history of\nyour two files (plus necessary trees and commits) but that won't come\nthis year.\n-- \nDuy\n"},{"id":"171574","messageId":"CALf5Ac3DcoB+Psgwys6NNOmTcyGmKj5dKhR7K8ardF6MsCCDwA@mail.gmail.com","threadId":"27843","inReplyTo":"CACsJy8C=LdcaQbc46ssc5=tTXyA-U4N4FAsqjnPyEqwYZuO4LA@mail.gmail.com","subject":"Re: git sparse checkout repo size","fromName":"gaoyong pan","fromEmail":"pan.gaoyong@gmail.com","sentAt":"2011-07-18T11:54:25Z","receivedAt":"2011-07-18T11:54:25Z","isPatch":false,"sender":{"key":"pan.gaoyong@gmail.com","avatar":null},"body":"2011/7/18 Nguyen Thai Ngoc Duy <pclouds@gmail.com>:\n> The ideal\n> solution would be narrow/sparse clone where you only fetch history of\n> your two files (plus necessary trees and commits) but that won't come\n> this year.\n> --\n> Duy\n>\n\nI need to push back so sparse clone is the best solution, it must be\nvery difficult to implement so it won't be released in this year?\n\n-- \nBest Regards\nLinux user #384184\n@ http://counter.li.org/\n"},{"id":"171575","messageId":"CACsJy8AEcQ-Wh2KrNDQ03fnabT3OFGgVCmWkOZ6BH7=ujgsRVg@mail.gmail.com","threadId":"27843","inReplyTo":"CALf5Ac3DcoB+Psgwys6NNOmTcyGmKj5dKhR7K8ardF6MsCCDwA@mail.gmail.com","subject":"Re: git sparse checkout repo size","fromName":"Nguyen Thai Ngoc Duy","fromEmail":"pclouds@gmail.com","sentAt":"2011-07-18T12:25:58Z","receivedAt":"2011-07-18T12:25:58Z","isPatch":false,"sender":{"key":"pclouds@gmail.com","avatar":"https://avatars.githubusercontent.com/u/720?v=4"},"body":"On Mon, Jul 18, 2011 at 6:54 PM, gaoyong pan <pan.gaoyong@gmail.com> wrote:\n> I need to push back so sparse clone is the best solution, it must be\n> very difficult to implement so it won't be released in this year?\n\nBecause nobody is working on it currently (I mean sparse/narrow clone.\nThere are alternatives, you can search the archive). I had a WIP some\ntime ago but there are still problems to be resolved before moving it\nforward. But I'm currently busy with pathspec work. Even if I have\ntime for it, such a big feature may get months to be accepted. Anybody\nis welcome to give it a try though.\n-- \nDuy\n"}]}