I added an arbitrary upstream remote thinking that I could just
git diff the upstream remote's master. Turns out I needed to run git
pull --all in order to be able to diff the file (I forgot that step).
    Could this error message be improved for interactive commands by
first checking to see whether or not the path starts with a remote,
then recommend that the remote be pulled? If this seems sane, I could
whip up a patch and post it in a github pull request.

$ git remote add pkohut [...]
$ git diff upstream/master -- conf/ | wc -l
$ git diff pkohut/master -- conf/ | wc -l
fatal: bad revision 'pkohut/master'
$ git pull --all
Fetching origin
Fetching upstream
Fetching pkohut
$ git diff pkohut/master -- conf/ | wc -l
$ git --version; uname -a
git version 1.7.9
CYGWIN_NT-6.1 ZL00757 1.7.25(0.270/5/3) 2013-08-31 20:37 x86_64 Cygwin
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to