{"thread":{"id":"59262","subject":"FR: make git clone --depth and --shallow-since produce maximal set of commits","startedAt":"2023-02-17T21:22:40Z","lastAt":"2023-02-17T21:22:40Z","messageCount":1,"participants":["Jonathan Mayer"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"472270","messageId":"CAFAmCQDJ0qEn8ZpY-DJ+M6vdBm12hwr=QDeM4GSY5=fZtFxzPg@mail.gmail.com","threadId":"59262","inReplyTo":null,"subject":"FR: make git clone --depth and --shallow-since produce maximal set of commits","fromName":"Jonathan Mayer","fromEmail":"jonathan@enfabrica.net","sentAt":"2023-02-17T21:21:58Z","receivedAt":"2023-02-17T21:22:40Z","isPatch":false,"sender":{"key":"jonathan@enfabrica.net","avatar":null},"body":"Problem: \"git clone --shallow-since 2022-12-01 --depth 1\" recently\nfailed with \"fatal: the remote end hung up unexpectedly\" because the\nrepo happened to not have any sufficiently recent commits.  I was\nhoping that by also specifying \"--depth 1\" that I would get at least\none commit, but it seems combining these options produces an\nintersection of the available commits (in my case, zero).\n\nObviously I can work around this but,\n\nProposed change: It would be useful if we changed the behavior of\nthese flags specified together to produce a union of commits instead\nof an intersection.\n\nI doubt there's a lot of prior art use cases depending on the old\nbehavior.  What do you think?\n\nThanks!  - Jonathan.\n"}]}