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

Re: Bug: fetch with deepen shortens history

From
BSBenjamin Stein <benji_stein@hotmail.com>
Date
Aug 4, 2023, 18:22 UTC
Message-ID
<MW4P223MB07081836921092F561B2DA709F08A@MW4P223MB0708.NAMP223.PROD.OUTLOOK.COM>
> I think in most cases, people doing shallow clones for testing mainline
> branch of whatever project they're hacking. If at some later date they
> wish to deepen their clones, they can do that up to specified date:

Yup, that makes sense to me. And it would make sense if it was up to a specified date, but I specifically want to reference a branch (which could move forward) so we can generate commits since then. You could imagine it being useful as "docs since last released version" where you don't need a tag for it, you can reference the release branch.

It's nice to be ably to rely on the fact that git refs can change, and so my script can continue to work without needing an update every time. I guess I could pull the ref and then use the date, but that (a) relies on nothing else happening around then, and (b) seems to be exactly what --shallow-exclude wants to do.

> Thanks for the script that you provided.
You bet. As a fellow engineer, I know how helpful perfectly reproducible steps can be. :)
-Benji
Message 1 of 1 in “Re: Bug: fetch with deepen shortens history”
  1. Benjamin SteinAug 4, 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.