When scanning for the right type of SCMTool for a repository, we ask each
SCMTool to try to provide information on the repository. If we can get
something useful out of it, we assume the tool is valid.
The Git tool is asking for that data and is computing the tracking branch
up-front, in all cases. It might be nice to only fetch when we need it, and
we know there's a lot of work that needs to be done to refactor this code
and clean it up. Would you mind filing a bug to help us track this?
Christian Hammond - chip...@chipx86.com
Review Board - http://www.reviewboard.org
VMware, Inc. - http://www.vmware.com
On Tue, Dec 4, 2012 at 11:03 AM, Matthew Woehlke
> I'm seeing this out of post-review:
> post-review --revision-range=<SHA1>:<SHA2> --output-diff --debug
>> RBTools 0.4.1
>>>> Home = /home/matthew
>>>> HTTP GETting api/
>>>> HTTP GETting https://manticore/api/info/
>>>> Using the new web API
>>> Failed to execute command: ['git', 'merge-base', 'origin/master',
> fatal: Not a valid object name origin/master
> Mind you, there is indeed no origin/master in this particular repository.
> However, I am confused why post-review is even attempting to determine a
> merge base in this case, given that I have specified a revision range. Is
> this expected behavior?
> If I add '--tracking-branch=<SHA1>' then all is well...
> Want to help the Review Board project? Donate today at
> http://www.reviewboard.org/**donate/ <http://www.reviewboard.org/donate/>
> Happy user? Let us know at
> To unsubscribe from this group, send email to reviewboard+unsubscribe@**
> googlegroups.com <reviewboard%2bunsubscr...@googlegroups.com>
> For more options, visit this group at http://groups.google.com/**
> group/reviewboard?hl=en <http://groups.google.com/group/reviewboard?hl=en>
Want to help the Review Board project? Donate today at
Happy user? Let us know at http://www.reviewboard.org/users/
To unsubscribe from this group, send email to
For more options, visit this group at