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

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

From
Miklos Vajna <vmiklos@frugalware.org>
Date
Nov 21, 2008, 22:18 UTC
Message-ID
<20081121221826.GM21815@genesis.frugalware.org>
In-Reply-To
<ee2a733e0811211341j1e49fad7o64577605951fa5c0@mail.gmail.com>
On Fri, Nov 21, 2008 at 04:41:57PM -0500, Leo Razoumov <slonik.az@gmail.com> wrote:
Show 6 quoted lines
> 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.

Actually fetch - at a core level - isn't symmetric to push, the protocol is completely different. I haven't checked the source, but I suppose that the push protocol has "dry run" support, while the fetch one doesn't have.

Previous: Leo RazoumovNext: Baz
Message 2 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.