Hi everyone,
Currently the templates use comment.filediff.dest_file directly in review
emails and in the review comments. While this looks fairly good for VCSes
like git or svn, it is pretty unreadable in case of Clear Case (it's pretty
common for Clear Case extended paths to be over few hundre
Hi everyone,
The post-review ClearCase client is supposed to be working both with
dynamic and snapshot views. Although, in case of snapshot views it
fails when review contains new files.
The problem is related to the diff_directories() function which
doesn't work with snapshot views.
Additionally
On Mon, Oct 15, 2012 at 3:22 PM, Peer wrote:
> the diff uploaded with post-review also show err with similar scenario (i.e
> view diff works fine for a while and get the err after some time)
> could you please help assist in resolving this error.
Was the file renamed or removed before the view di
On Mon, Oct 15, 2012 at 4:06 PM, Peer wrote:
> i tried using uploading diff generated by diff -uN/diff -c (or) post-review
> (submit diff of checked-out files), all of them diff get broken after some
> time)
If you submitted patch using post-review, the extended_path should
include version inform
On Fri, Feb 8, 2013 at 7:47 AM, Sateesh Hegde wrote:
> I am new to reviewboard. Just installed 1.7. I have a ClearCase repository
> and mostly we use dynamic views. Can it work with the remote clearcase view
> host ? Or Does it require me to install the clearcase client on the hosting
> machine ?
