Git Mailing List Archive mirror
 help / color / mirror / Atom feed
* FR: make git clone --depth and --shallow-since produce maximal set of commits
@ 2023-02-17 21:21 Jonathan Mayer
  0 siblings, 0 replies; only message in thread
From: Jonathan Mayer @ 2023-02-17 21:21 UTC (permalink / raw)
  To: git

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.

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2023-02-17 21:22 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-02-17 21:21 FR: make git clone --depth and --shallow-since produce maximal set of commits Jonathan Mayer

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).