Status: New
Owner: ----
Labels: Type-Defect Priority-Medium
New issue 2816 by [email protected]: post-review (git) fails
unnecessarily with explicit revision range, if implicit tracking branch
does not exist
http://code.google.com/p/reviewboard/issues/detail?id=2816
What version are you running?
0.4.2
What steps will reproduce the problem?
1. Set up a git repository with no origin/master
2. post-review --revision-range=<rev1>:<rev2> --output-diff
What is the expected output? What do you see instead?
post-review fails trying to query git repository about origin/master
What operating system are you using? What browser?
Linux
Please provide any additional information below.
It seems that post-review should not need to be poking around the
repository looking for a merge base when given an explicit revision range.
As mentioned on the mailing list, this is probably related to post-review's
pre-processing 'poke the repo' functionality. Since the problem can be
avoided by also adding --tracking-branch=<rev1>, perhaps this should be
default behavior when specifying an explicit revision range?
--
You received this message because you are subscribed to the Google Groups
"reviewboard-issues" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/reviewboard-issues?hl=en.
