Re: "warning: no common commits" triggered due to change of remote's IP address?

On Mon, Mar 2, 2009 at 12:56 AM, Thomas Rast [off-list ref] wrote:

Actually this should name the remote's idea of the ref, i.e.,

 git fetch-pack -v $url refs/heads/home 2>&1 \
 | git name-rev --stdin

Sorry, but I had since done a git fetch from home using the local IP
address before I realized that you would want to try more
experiments on it. But that "local" git-fetch did not emit the
"warning: no common commits" message and was fast. Maybe the majority
of the fetch I had started at the Internet cafe but terminated had
done a lion share of the work already, and the speedy local fetch
finished up the leftovers.

But for completeness sake, I did as you said on the now (mostly) up to
date repo:

  git fetch-pack -v <remote_ip_address>:git.repos/environ.git
refs/heads/home 2>&1 \
   | git name-rev --stdin
  Server supports multi_ack
  Server supports side-band-64k
  Marking 67cb0521a93778a9d9c4d8f4608f2c6c796a7558 (home) as complete
  already have 67cb0521a93778a9d9c4d8f4608f2c6c796a7558 (home) (refs/heads/home)
  67cb0521a93778a9d9c4d8f4608f2c6c796a7558 (home) refs/heads/home

where <remote_ip_address> is the remote IP address, and not the usual
local IP address that is referenced in .git/config.

What does "Marking ... as complete" mean?

Is the git-fetch-pack method shown above the only way to get a report
of what git finds out of date? Seems that git-fetch-pack actually
downloads objects, instead of just reporting what it would do without
actually doing it.

Brent