{"thread":{"id":"65807","subject":"Re: [PATCH] clone: accept DEPTH env var as fallback for --depth","startedAt":"2026-06-14T08:13:56Z","lastAt":"2026-06-14T08:13:56Z","messageCount":1,"participants":["Hadrien Loge"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"545486","messageId":"CADeHOfx3O9KpORQdLmvb0BPhaHUGmtxoyDEqySNQY_d6+ia7VA@mail.gmail.com","threadId":"65807","inReplyTo":null,"subject":"Re: [PATCH] clone: accept DEPTH env var as fallback for --depth","fromName":"Hadrien Loge","fromEmail":"hadrien.loge@gmail.com","sentAt":"2026-06-14T08:13:53Z","receivedAt":"2026-06-14T08:13:56Z","isPatch":true,"body":"> So say someone has this set in their environment and then they run a\nscript that clones a repository and runs `git describe`.  That no longer\nworks and the script fails because it assumed that it had history.\n\nThat is insightful but that I fail to see how that makes `git` less capable.\nAs Junio pointed there already other ENV vars that do _less_ useful stuff\n\nAs to breakage, this is mostly for packaging in clean chroots.\nIf a \"history\" feature is asked, obviously you skip setting this.\n\nAnd yes the packages need network to build because they\nare mostly user generated. For example applying patches\nto other repos, before building tar archives.\n\nI also fail to see how that would affect existing flows at all?\n\n> because shallow fetches are _extremely_ expensive to serve\n\nThat seems like an unrelated issue to my patch yet is also interesting\nas to why that would be the case. I might actually want to dig into.\nBecause to me, I was saving electrons, at least on my end.\nAnd saving time to other packagers.\n\nThanks for the thoughtful reply. I hope this patch can still be considered\nHade\n"}]}