Does this refer to the following error?
c:\src\chromium\src>git try --bot win
Loaded authentication cookies from c:/Users/scottmg/.codereview_upload_cookies
Command git diff --name-status -r refs/remotes/origin/trunk...
c:\src\chromium\src returned non-zero exit status 128
fatal: invalid diff option/value: -r
I tried deleting rmdir /s/q depot_tools\git_cl per your instructions,
but did not help. Do I need to install a new version of git perhaps?
> --
> Chromium Developers mailing list: chromi...@chromium.org
> View archives, change email options, or unsubscribe:
> http://groups.google.com/a/chromium.org/group/chromium-dev
>
Anyway, running
git diff --name-status -r refs/remotes/origin/trunk... c:\src\chromium\src
errors out with the same error as git try does (invalid diff
option/value -r), and git --version is
git version 1.7.6.msysgit.0
I seem to get the same error with a similar style command line on a
linux machine with git version 1.7.3.1.
So "-r" is technically not a valid option to anything but
git-diff-tree, but git's diff argument parsing is heavily shared, so
it's a no-op 99% of the time. (The "-r" option is handled in
revision.c)
You however hit seem to have hit diff_no_index, where the option is
invalid. diff_no_index is run when you run git with --no-index (which
you aren't doing), OR when you use git diff outside a repo. So my
guess is that git doesn't think you're CWD is actually inside a proper
git repo.
And yes, diff_no_index could fail with a better error message here.
@maruel - you might want to remove the "-r" inside scm.py on this git
call - it's a no-op 99% of the time, but in this case it's hiding a
slightly better error message, which would likely be "error: Could not
access 'refs/remotes/origin/trunk...'" without the "-r".)
j.
Thanks Jay. Assuming your psychic debugging is correct (and I do
indeed get the error you suggest if I remove -r), that raises the
question: why does git think it's not a git repo? i.e.
c:\src\chromium\src>type .git\refs\remotes\origin\trunk
05b7b785a7c133bbde6dc355b4d4637a2a2176d0
c:\src\chromium\src>git cat-file -p 05b7b785a7c133bbde6dc355b4d4637a2a2176d0
tree 436c37851df42c10fa0914d3f6e1e9989edbbf45
parent c97d4bf90ce19a32376164c409c8071f62dcf921
...
I added a few prints in scm.py but nothing is jumping out as broken looking.
I assume this is only happening for me? If so, since I have to switch
git "styles" anyway, I'll just take this clone Out Behind The Barn,
switch to NewGit-stylez and we can all pretend this never happened.
Thanks Jay. Assuming your psychic debugging is correct (and I doindeed get the error you suggest if I remove -r), that raises the
question: why does git think it's not a git repo? i.e.
c:\src\chromium\src>type .git\refs\remotes\origin\trunk
05b7b785a7c133bbde6dc355b4d4637a2a2176d0
c:\src\chromium\src>git cat-file -p 05b7b785a7c133bbde6dc355b4d4637a2a2176d0
tree 436c37851df42c10fa0914d3f6e1e9989edbbf45
parent c97d4bf90ce19a32376164c409c8071f62dcf921
...
I added a few prints in scm.py but nothing is jumping out as broken looking.
I assume this is only happening for me? If so, since I have to switch
git "styles" anyway, I'll just take this clone Out Behind The Barn,
switch to NewGit-stylez and we can all pretend this never happened.