Comment #19 on issue 658 by gjun...@gmail.com: Error : The patch
to 'filepath' didn't apply cleanly.
http://code.google.com/p/reviewboard/issues/detail?id=658
It's an existing file in CVS.
We experienced that the same file change sometime works, sometimes not.
--
You received this message
Comment #17 on issue 658 by gjun...@gmail.com: Error : The patch
to 'filepath' didn't apply cleanly.
http://code.google.com/p/reviewboard/issues/detail?id=658
I attached the .rej file as below for information because I can not figure
out the problem from the file.
Thanks!
Attachments:
Comment #18 on issue 658 by trowb...@gmail.com: Error : The patch
to 'filepath' didn't apply cleanly.
http://code.google.com/p/reviewboard/issues/detail?id=658
Is this a newly-added file?
--
You received this message because you are subscribed to the Google Groups
reviewboard-issues group.
Comment #16 on issue 658 by trowb...@gmail.com: Error : The patch
to 'filepath' didn't apply cleanly.
http://code.google.com/p/reviewboard/issues/detail?id=658
Getting rejects usually indicates some problem with how the diff was
generated. Check the .rej file to see what failed.
--
You
Comment #15 on issue 658 by gjun...@gmail.com: Error : The patch
to 'filepath' didn't apply cleanly.
http://code.google.com/p/reviewboard/issues/detail?id=658
I would strongly vote and appreciate a solution/suggestions on this issue:
Our environment is reviewboard 1.6.14 on Ubuntu 12.04
Comment #14 on issue 658 by darshanrn: Error : The patch to 'filepath'
didn't apply cleanly.
http://code.google.com/p/reviewboard/issues/detail?id=658
I get the same problem Exception: The patch to 'file' didn't apply
cleanly. This is a very intermittent issue. Earlier the diff was
Comment #12 on issue 658 by sanjiv.raj: Error : The patch to 'filepath'
didn't apply cleanly.
http://code.google.com/p/reviewboard/issues/detail?id=658
I also encountered this issue after a perforce to svn migration. Fixing the
ident
(RCS) strings solved the issue.
The diff provided by svn
Comment #5 on issue 658 by chipx86: Error : The patch to 'filepath'
didn't apply cleanly.
http://code.google.com/p/reviewboard/issues/detail?id=658
This usually indicates that the revision is wrong. How was the diff
generated, and
what repository type?
--
You received this message because
Comment #6 on issue 658 by manjunath.shiva: Error : The patch
to 'filepath' didn't apply cleanly.
http://code.google.com/p/reviewboard/issues/detail?id=658
diff is generated on UNIX and copied from screen to windows and that was the
problem. Now he tried did an ftp and it worked. With the
Comment #7 on issue 658 by chipx86: Error : The patch to 'filepath'
didn't apply cleanly.
http://code.google.com/p/reviewboard/issues/detail?id=658
But how was the diff generated? What tool, parameters?
Copying from screen to windows will break things. I assume you mean
copy/paste. That
Comment #8 on issue 658 by manjunath.shiva: Error : The patch
to 'filepath' didn't apply cleanly.
http://code.google.com/p/reviewboard/issues/detail?id=658
diff was generated using cvs diff -u amuoci.c amuoci.diff on UNIX. Here
use made a
mistake of copy/paste from UNIX shell to Windows.
Comment #9 on issue 658 by manjunath.shiva: Error : The patch
to 'filepath' didn't apply cleanly.
http://code.google.com/p/reviewboard/issues/detail?id=658
I tried with latest post-review version 0.8. The problem is we do have post-
review.exe so we need to use UWIN / MKS / Cigwin to run this
Comment #10 on issue 658 by chipx86: Error : The patch to 'filepath'
didn't apply cleanly.
http://code.google.com/p/reviewboard/issues/detail?id=658
Ah yeah, that's a potential problem for now. However, I do plan to get a
post-review.exe into the next release.
--
You received this message
Comment #2 on issue 658 by miguel.rgonzalez: Error : The patch
to 'filepath' didn't apply cleanly.
http://code.google.com/p/reviewboard/issues/detail?id=658
same issue here.
I get the same error when posting reviews for newly created file (nothing
to diff
against)
--
You received this
Issue 658: Error : The patch to 'filepath' didn't apply cleanly.
http://code.google.com/p/reviewboard/issues/detail?id=658
New issue report by sudarsan:
*NOTE: Do not post confidential information in this bug report.*
What's the URL of the page containing the problem?
15 matches
Mail list logo
