Is it just me, or do those paths look identical? Those are paths relative to
the repository root, and doesn't seem to have anything to do with remote
servers.
On Feb 19, 2014, at 10:40 AM, Allen
zhangsan8...@gmail.commailto:zhangsan8...@gmail.com wrote:
After a code review is created, there`s
Agreed. This looks exactly like what I'd expect to see. It's a typical
result from running 'svn diff'.
Christian
On Wednesday, February 19, 2014, Andrew Hills (anhills) anhi...@cisco.com
wrote:
Is it just me, or do those paths look identical? Those are paths relative
to the repository root,
Yes, that`s the relative path to the Repository in the SVN server. The
thing is when I run svn dff, I get these paths:
Index: src/ReviewBoardTest.java
===
--- src/ReviewBoardTest.java(revision 167)
+++ src/ReviewBoardTest.java
When I run svn dff, I get these paths:
--- src/ReviewBoardTest.java(revision 167)
+++ src/ReviewBoardTest.java(working copy)
The paths above are my local ones, and I can use these paths do a apply
patch.
While when I run rbt diff or rbt post, I got those paths, and I can not
use those
That's what patch's -p option is for.
If your local path is src/ReviewBoardTest.java, and the diff has
/trunk/ReviewBoardTest/src/ReviewBoardTest.java, you can apply the patch
using:
patch -p3 ReviewBoardTest.java
-David
On Wed, Feb 19, 2014 at 1:26 PM, Allen zhangsan8...@gmail.com wrote:
Cool, thanks. Another way is to generate a patch file using the SVN and
then create a code review with that patch file, then the paths wont mess up.
On Wednesday, February 19, 2014 4:32:26 PM UTC-5, David Trowbridge wrote:
That's what patch's -p option is for.
If your local path is
