I ended up using h instead of hb and then restarted memcached and I was 
back in business

On Tuesday, March 20, 2012 2:58:54 PM UTC-5, JeffG wrote:
> Hey John, I am seeing the same issue - did you ever get this figured out?
> On Wednesday, September 1, 2010 4:04:51 PM UTC-5, John Mcfarlane wrote:
>> Context around my question, I'm running the following: 
>> Git 
>> Gitweb 
>> Reviewboard 1.5 RC1 
>> When configuring a remote git repo (without a local repo on disk) I 
>> used the following configuration (which seems to work perfectly): 
>> path: git://hostname/repo.git 
>> mirror: ssh://hostname/var/git/repo.git 
>> mask: http://hostname/?p=repo.git;a=blob_plain;f=<filename>;h=<revision> 
>> So again, the above seems to work perfectly.  I'm able to post 
>> reviews, including both binary and ascii files.  So here's my 
>> question... 
>> The docs here: 
>> http://www.reviewboard.org/docs/manual/dev/admin/management/repositories/#gitweb
>> indicate that you should use the HTTP GET arg: "hb=<revision>".  When 
>> I do that, I get the following (formatted slightly) when posting the 
>> review: 
>> >>> Got API Error 207 (HTTP code 200): The file was not found in the 
>> repository 
>> >>> Error data: 
>> {u'deprecated': {u'in_version': u'1.5'}, 
>>  u'stat': u'fail', 
>>  u'file': u'.reviewboardrc', 
>>  u'err': {u'msg': u'The file was not found in the repository', 
>> u'code': 207}, 
>>  u'revision': u'0ea7701cc2969b1b2e8c771e302662b6c7e68466' 
>> } 
>> But if I change the mask to use the HTTP GET arg: "h=<revision>"... it 
>> works perfectly.  I tried to look up the gitweb api to see what the 
>> difference is between "h" and "hb" but didn't really find anything. 
>> Is it possible that the value should be "h" and the doc should to be 
>> corrected?  Or is my config jacked up in some way that it's working 
>> and shouldn't' be? 
>> Thanks in advance for the help :) 
>> Best regards, 
>> John M. 

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 

Reply via email to