Re: Can anybody do review?

Thanks for quick response. But if user has not user level permissions to do review, which we set at the time of user creation, then also he can do review. Is this designed in that way too? If yes then whats significance of the user level permissions that we set up? I apologies if it has been

Re: Can anybody do review?

Those permissions are provided automatically by Django. They're for the admin UI only, and do not govern the functionality of Review Board itself. Christian -- Christian Hammond - [EMAIL PROTECTED] VMware, Inc. On Mon, Oct 6, 2008 at 11:41 PM, Atul Phalke [EMAIL PROTECTED]wrote: Thanks for

Re: Cannot login after fresh install under apache http.

Can you try Django 1.0 instead of 1.1 alpha? I think we have some issues with 1.1 at the moment. Christian -- Christian Hammond - [EMAIL PROTECTED] VMware, Inc. On Mon, Oct 6, 2008 at 11:39 PM, mascha [EMAIL PROTECTED] wrote: Hey, I tried the latest svn version and followed the wiki

Re: Using Perforce and Pre-Reviews

A better name for post-review is post-a-review. As long as you move the files you wish to review out of the default changelist you can use post-review. On Tue, Oct 7, 2008 at 5:41 AM, Marcos [EMAIL PROTECTED] wrote: Greetings. I installed reviewboard, and it seems to work ok using

Re: Cannot login after fresh install under apache http.

On 7 Okt., 08:58, Christian Hammond [EMAIL PROTECTED] wrote: Can you try Django 1.0 instead of 1.1 alpha? I think we have some issues with 1.1 at the moment. With version 1.0 I have the same problem. --~--~-~--~~~---~--~~ You received this message because you

Re: Using Perforce and Pre-Reviews

Now I get this error: Unable to parse diff header: : Invalid argument This is the debug output J:\post-review.py -n --debug --diff-only 56843 Repository info 'Path: perforce.server.com:1666, Base path: None, Supports changesets: True' Generating diff for changenum 56843 p4 describe -s

Re: Using Perforce and Pre-Reviews

I think the issue might be on this line: diff -urNp c:\docume~1\marcosp\locals~1\temp\tmpvzainx C:/CODE\branches\my_branch\client\GUI\StartWindow.cpp Slash and backslash together, does not sound right. Any ideas? On Oct 7, 4:42 pm, Marcos [EMAIL PROTECTED] wrote: Now I get this error:

Using Perforce and Pre-Reviews

Greetings. I installed reviewboard, and it seems to work ok using post-review, the only issue with is is that (as the name says) post-review is to make reviews already submitted, on what I want to do is use it on not committed changes. I use perforce, and that is why I am using post-review (as

Re: How are comments associated with code?

They aren't brought along as people commit changes to code. ok, as far as I understand now the commits are stored with the diffs in reviewboard (or the database it uses). --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google

Re: Help with Apache

On Oct 6, 5:12 am, demjanenko [EMAIL PROTECTED] wrote: On Oct 5, 11:14 pm, flyincognito [EMAIL PROTECTED] wrote: I managed to get this going - I played with it a bit, and my paths must have been set up wrong. Hi! I have similar problem. Can you post your corrected vhost config? No

Issue 682 in reviewboard: Cannot login after fresh install under apache http.

Issue 682: Cannot login after fresh install under apache http. http://code.google.com/p/reviewboard/issues/detail?id=682 Comment #2 by [EMAIL PROTECTED]: I tried with version 1.0.0 final and have the same issue. -- You received this message because you are listed in the owner or CC fields of

Issue 401 in reviewboard: Comments should be inserted into diff below lines being discussed, instead of in dialog box

Issue 401: Comments should be inserted into diff below lines being discussed, instead of in dialog box http://code.google.com/p/reviewboard/issues/detail?id=401 Comment #5 by chipx86: The key difference with the popup window is that we get intelligently place it initially but give users the