git/list[1] front-page[2] threads[3] people[4] search[5] about
 

FR: make git clone --depth and --shallow-since produce maximal set of commits

From
JMJonathan Mayer <jonathan@enfabrica.net>
Date
Feb 17, 2023, 21:21 UTC
Message-ID
<CAFAmCQDJ0qEn8ZpY-DJ+M6vdBm12hwr=QDeM4GSY5=fZtFxzPg@mail.gmail.com>
Problem: "git clone --shallow-since 2022-12-01 --depth 1" recently
failed with "fatal: the remote end hung up unexpectedly" because the
repo happened to not have any sufficiently recent commits.  I was
hoping that by also specifying "--depth 1" that I would get at least
one commit, but it seems combining these options produces an
intersection of the available commits (in my case, zero).
Obviously I can work around this but,

Proposed change: It would be useful if we changed the behavior of these flags specified together to produce a union of commits instead of an intersection.

I doubt there's a lot of prior art use cases depending on the old behavior. What do you think?

Thanks!  - Jonathan.
Message 1 of 1 in “FR: make git clone --depth and --shallow-since produce maximal set of commits”
  1. Jonathan MayerFeb 17, 2023

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.