{"thread":{"id":"64032","subject":"Shallow clone support in v3.0 and beyond?","startedAt":"2025-08-25T23:34:06Z","lastAt":"2025-09-10T11:13:09Z","messageCount":3,"participants":["Bagas Sanjaya","Patrick Steinhardt"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"524903","messageId":"aKzy6naLtdeq7Tgn@archie.me","threadId":"64032","inReplyTo":null,"subject":"Shallow clone support in v3.0 and beyond?","fromName":"Bagas Sanjaya","fromEmail":"bagasdotme@gmail.com","sentAt":"2025-08-25T23:34:02Z","receivedAt":"2025-08-25T23:34:06Z","isPatch":false,"sender":{"key":"bagasdotme@gmail.com","avatar":"https://avatars.githubusercontent.com/u/40219486?v=4"},"body":"Hi,\n\nAskar Safin <safinaskar@zohomail.com> posted on the ML about his complaints\nregarding grafts removal in v3.0+ (see [1] for the full thread). He also\nbriefly mentioned future of shallow clones (aka git clone --depth=1).\n\nThe question is: If grafts support is removed, then how can shallow clones\nbe implemented in terms of git-replace(1)? What about its implementation\ndetails? How about unshallowing (git fetch --unshallow)?\n\nThanks.\n\n[1]: https://lore.kernel.org/git/198c29e9058.119e3a5c065010.5888624019176274871@zohomail.com/T/#t\n\n-- \nAn old man doll... just what I always wanted! - Clara\n"},{"id":"526022","messageId":"aMFcH2nfKO-DZcwm@pks.im","threadId":"64032","inReplyTo":"aKzy6naLtdeq7Tgn@archie.me","subject":"Re: Shallow clone support in v3.0 and beyond?","fromName":"Patrick Steinhardt","fromEmail":"ps@pks.im","sentAt":"2025-09-10T11:08:15Z","receivedAt":"2025-09-10T11:08:22Z","isPatch":false,"sender":{"key":"ps@pks.im","avatar":"https://avatars.githubusercontent.com/u/4056630?v=4"},"body":"Hi,\n\nOn Tue, Aug 26, 2025 at 06:34:02AM +0700, Bagas Sanjaya wrote:\n> Hi,\n> \n> Askar Safin <safinaskar@zohomail.com> posted on the ML about his complaints\n> regarding grafts removal in v3.0+ (see [1] for the full thread). He also\n> briefly mentioned future of shallow clones (aka git clone --depth=1).\n> \n> The question is: If grafts support is removed, then how can shallow clones\n> be implemented in terms of git-replace(1)? What about its implementation\n> details? How about unshallowing (git fetch --unshallow)?\n> \n> Thanks.\n> \n> [1]: https://lore.kernel.org/git/198c29e9058.119e3a5c065010.5888624019176274871@zohomail.com/T/#t\n\nI think the BreakingChanges document could use a revamp in that regard.\nThe mechanism used to implement shallow clones is of course _not_ going\naway, and the internal mechanism to facilitate this will go away.\n\nSo the intention really only to remove \".git/info/grafts\" as a\nuser-visible mechanism. Users should exclusively use git-replace(1).\n\nPatrick\n"},{"id":"526023","messageId":"dca4e74e-26ae-401d-bac9-f8b6f13296ef@gmail.com","threadId":"64032","inReplyTo":"aMFcH2nfKO-DZcwm@pks.im","subject":"Re: Shallow clone support in v3.0 and beyond?","fromName":"Bagas Sanjaya","fromEmail":"bagasdotme@gmail.com","sentAt":"2025-09-10T11:13:05Z","receivedAt":"2025-09-10T11:13:09Z","isPatch":false,"sender":{"key":"bagasdotme@gmail.com","avatar":"https://avatars.githubusercontent.com/u/40219486?v=4"},"body":"On 9/10/25 18:08, Patrick Steinhardt wrote:\n> Hi,\n> \n> On Tue, Aug 26, 2025 at 06:34:02AM +0700, Bagas Sanjaya wrote:\n>> Hi,\n>>\n>> Askar Safin <safinaskar@zohomail.com> posted on the ML about his complaints\n>> regarding grafts removal in v3.0+ (see [1] for the full thread). He also\n>> briefly mentioned future of shallow clones (aka git clone --depth=1).\n>>\n>> The question is: If grafts support is removed, then how can shallow clones\n>> be implemented in terms of git-replace(1)? What about its implementation\n>> details? How about unshallowing (git fetch --unshallow)?\n>>\n>> Thanks.\n>>\n>> [1]: https://lore.kernel.org/git/198c29e9058.119e3a5c065010.5888624019176274871@zohomail.com/T/#t\n> \n> I think the BreakingChanges document could use a revamp in that regard.\n> The mechanism used to implement shallow clones is of course _not_ going\n> away, and the internal mechanism to facilitate this will go away.\n> \n> So the intention really only to remove \".git/info/grafts\" as a\n> user-visible mechanism. Users should exclusively use git-replace(1).\n\nOK, thanks!\n\n-- \nAn old man doll... just what I always wanted! - Clara\n"}]}