The upstream tracker would probably be a better place. We're only
running code that has landed upstream, so this is unlikely to be a local
bug (especially considering the behavior described). Gerrit's tracker
is here:
To work around the immediate problem, I'd recommend downloading the
change locally with the "git fetch" and "git checkout" commands listed
on the page in Gerrit; you can then run "git diff" locally to see the
change.
From James Blair...
The upstream tracker would probably be a better place. We're only
running code that has landed upstream, so this is unlikely to be a local
bug (especially considering the behavior described). Gerrit's tracker
is here:
https:/ /code.google. com/p/gerrit/ issues/ list
To work around the immediate problem, I'd recommend downloading the
change locally with the "git fetch" and "git checkout" commands listed
on the page in Gerrit; you can then run "git diff" locally to see the
change.
-Jim