{"thread":{"id":"35205","subject":"previewing \"git pull\"","startedAt":"2013-10-26T03:23:10Z","lastAt":"2013-10-26T03:23:10Z","messageCount":1,"participants":["Perry Hutchison"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"229544","messageId":"526b359e.dmR4kAHrnCsJVbAm%perryh@pluto.rain.com","threadId":"35205","inReplyTo":null,"subject":"previewing \"git pull\"","fromName":"Perry Hutchison","fromEmail":"perryh@pluto.rain.com","sentAt":"2013-10-26T03:23:10Z","receivedAt":"2013-10-26T03:23:10Z","isPatch":false,"sender":{"key":"perryh@pluto.rain.com","avatar":null},"body":"In git 1.7.0.4, what's the correct way to preview what a \"git pull\"\nwould do, without actually doing it?  Unlike most git subcommands,\npull seems not to understand --dry-run:\n\n$ git pull --dry-run\nsed: can't read {pathname suppressed}/.git/FETCH_HEAD: No such file or directory\nYou asked to pull from the remote '--dry-run', but did not specify\na branch. Because this is not the default configured remote\nfor your current branch, you must specify a branch on the command line.\n\nTrying the \"fetch\" part of pull by itself, at least fetch doesn't\nmistake --dry-run for a remote name, but it doesn't seem to\nimplement it either -- instead of a report of what it would do,\nthere's no output at all:\n\n$ git fetch --dry-run\n$\n\nI'm guessing that I may need to actually do the fetch in order\nfor git to know what the remote has, but then how would I find\nout exactly what merge command \"pull\" would have issued (so as\nto try adding --dry-run to it)?\n"}]}