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

why no "git fetch --dry-run" ?

From
LRLeo Razoumov <slonik.az@gmail.com>
Date
Nov 21, 2008, 21:41 UTC
Message-ID
<ee2a733e0811211341j1e49fad7o64577605951fa5c0@mail.gmail.com>

Hello List, I am curious why there is "git push --dry-run" and no "git fetch --dry-run" nor "git pull --dry-run". It would make sense to keep push/pull/fetch as symmetric as possible. For example, I just want to see which branches, if any, changed on a remote repository since my last fetch. "git fetch -v --dry-run" would be handy in this case.

--Leo--
Next: Miklos Vajna
Message 1 of 4 in “why no "git fetch --dry-run" ?”
  1. Leo RazoumovNov 21, 2008
  2. Miklos VajnaNov 21, 2008
  3. BazNov 21, 2008
  4. Junio C HamanoNov 22, 2008

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.