Thanks, it works. 2. As to using post-review instead of 'rbt post': in our set up, >> post-review works but 'rbt post' doesn't. The reason is that our SVN >> repository is configured in RB with file:// protocol, while developers >> access it using svn:// protocol. The reasons for this configuration is to >> reduce the load on the server (since RB is running on the same machine, why >> should it go over the network when it can access repository directly). This >> also allows RB to see the repository without a dedicated RB user. >> > > We're going to be improving the way that rbt post (and post-review) match > SVN repositories on the server. 0.5.5 will include this change: > https://reviews.reviewboard.org/r/5248/ , which will let you pass in the > repository name through the --repository-url flag (or associated REPOSITORY > config key). For the 0.6 release, we'll be separating this out into a > --repository setting. > Does this mean that every post-review invocation would have to be performed with this --repository-url option? Not very convenient, IMO. I think it would be much easier if RB - compared SVN repository UUIDs - these are guaranteed to be the same, regardless of how the repository is accessed OR - allowed to store this "repository URL" in the repository itself, same as it does with the URL to the ReviewBoard (this way, rbt can obtain the property from by running 'svn propget') OR - allowed to configure repositories with "also-can-be-accessed-as" list of URLs Regards, Alexey. > > -David > -- Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/ --- Sign up for Review Board hosting at RBCommons: https://rbcommons.com/ --- Happy user? Let us know at http://www.reviewboard.org/users/ --- You received this message because you are subscribed to the Google Groups "reviewboard" group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.