Hi Christian.
Many thanks for answer.
The fall back mechanism will work for us.
Let's see if some new needs appear on horizon.
Br
Aleksandar
On Fri, Aug 13, 2010 at 5:57 AM, Christian Hammond chip...@chipx86.comwrote:
Hi Aleksandar,
Our auth always falls back to standard auth for any users
Hi Adam,
There are a couple solutions to this.
One is to use something like LDAP as the One True Auth Backend for all
your servers. This is the easiest in that no custom code is
required. However, it does require that your other services support
LDAP and that you can easily switch all accounts
In this case, post-review should actually work. post-review with Subversion
shouid properly handle the case where you have new files that haven't been
committed yet that you want to put up for review. We did this all the time
with Review Board itself, before we switched over to Git.
Correct me if
Hi,
I want to integrate my SVN repo with Reviewboard. I added the
repo in the Database -- ScmTools -- Repositories and added the svn
repo path. In the New Review Request i don't see the svn repo in the
drop down list. I have installed pysvn in the /usr/lib/python2.4/site-
I have some particular files and directories in a codebase which need
review and can't figure out a way to simply post the entire files, as
they exist now, to Review Board. The code is managed with Mercurial
at the moment. I've been trying various incantations with post-review
and hg export and
On Aug 13, 2010, at 3:20 AM, Christian Hammond wrote:
Try renaming id_rsa_ipstreet to just id_rsa. This is what paramiko is
expecting to find in that directory.
Christian
Done. Same thing happens.
John
--
Want to help the Review Board project? Donate today at
Status: New
Owner:
Labels: Type-Enhancement Priority-Medium
New issue 1764 by ben.hollis: Show Perforce file types in diff view file
listing
http://code.google.com/p/reviewboard/issues/detail?id=1764
What version are you running?
1.0
What's the URL of the page this enhancement relates
