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

fetch unshallow fails to honor dry-run

From
Tim Janik <timj@gnu.org>
Date
Oct 25, 2015, 09:16 UTC
Message-ID
<562C9DD0.5040109@gnu.org>
Hey all,
git fetch --dry-run modifies the repository if --unshallow is passed:

$ git --version git version 2.1.4 $ git fetch --dry-run --unshallow remote: Counting objects: 30603, done. remote: Compressing objects: 100% (6843/6843), done. remote: Total 30603 (delta 24564), reused 29164 (delta 23386) Receiving objects: 100% (30603/30603), 5.42 MiB | 0 bytes/s, done. Resolving deltas: 100% (24564/24564), completed with 317 local objects. remote: Counting objects: 7, done. remote: Compressing objects: 100% (7/7), done. remote: Total 7 (delta 0), reused 6 (delta 0) Unpacking objects: 100% (7/7), done.

I actually tried --dry-run --unshallow in order to find a way to detect in a script if the current git repository is shallow or not. Better suggestions to find this out are very welcome.

-- 
Yours sincerely,
Tim Janik

https://testbit.eu/timj/
Free software author and speaker.
Next: Jeff King
Message 1 of 3 in “fetch unshallow fails to honor dry-run”
  1. Tim JanikOct 25, 2015
  2. Jeff KingNov 9, 2015
  3. Duy NguyenNov 14, 2015

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.