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

Re: no --dry-run to git-pull ?

From
Miklos Vajna <vmiklos@frugalware.org>
Date
Jul 4, 2008, 13:59 UTC
Message-ID
<20080704135944.GA4729@genesis.frugalware.org>
In-Reply-To
<912ec82a0807040656y1c48cba8m6f9981f6bb97b36a@mail.gmail.com>
On Fri, Jul 04, 2008 at 04:56:27PM +0300, Neshama Parhoti <pneshama@gmail.com> wrote:
> Isn't there a way to do a --dry-run with git-pull ?

Not really. But you can do a 'git fetch origin', then a 'git log master..origin/master', and it'll tell you what changes will be merged if you do a 'git merge origin/master'.

NOTES:
1) Replace origin and master with your repomte and branch.
2) If this sounds cryptic for you, then it might be an important info
that by default a pull is a fetch + a merge.
Previous: Neshama ParhotiNext: Neshama Parhoti
Message 2 of 4 in “no --dry-run to git-pull ?”
  1. Neshama ParhotiJul 4, 2008
  2. Miklos VajnaJul 4, 2008
  3. Neshama ParhotiJul 4, 2008
  4. Miklos VajnaJul 4, 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.