Also got some more emails from other users that are generating paths from
the IDE, so the path in those diffs may be something like
../root/path/to/File.java and when they try to submit a diff there is no
way to get it to work. They were able to make things work in ReviewBoard
1.6.11 by using
Hey
just wondering if there is a definite release date for ReviewBoard 2.0.16
--
Supercharge your Review Board with Power Pack:
https://www.reviewboard.org/powerpack/
Want us to host Review Board for you? Check out RBCommons:
https://rbcommons.com/
Happy user? Let us know!
Working on it right now :)
Christian
--
Christian Hammond - christ...@beanbaginc.com
Review Board - https://www.reviewboard.org
Beanbag, Inc. - https://www.beanbaginc.com
-Original Message-
From: Austin Wolfson awolf...@wordstream.com
Reply: reviewboard@googlegroups.com
On Thu, Jun 11, 2015 at 4:34 AM Christian Hammond christ...@beanbaginc.com
wrote:
Hey everyone,
We just released RBTools 0.7.4, which features compatibility fixes for
Python 2.6, TFS, Mercurial, amongst a few other improvements.
To get the latest release, head over to the RBTools Downloads
Status: Confirmed
Owner:
Labels: Type-Defect Priority-High Component-Reviews Project-ReviewBoard
SCM-Git
New issue 3884 by chip...@gmail.com: New Review Request page should take a
base commit ID
https://code.google.com/p/reviewboard/issues/detail?id=3884
What version are you running?
You shouldn't have to modify the diff files even if the paths include . and
..
For patches generated in the root of the repository, the base directory
should never have been ./, but /
A patch generated in a subdirectory but trying to give a full file path
(such as ../../trunk/path/File.java)