If patch was created
- From SVN Working Copy
- Using SVN-command
svn diff
instead of OS-specific
you can see in patch-file information about patch-point.
Patch as svn diff
between two revisions in repository
...
--- trunk/G1.txt (revision 3)
+++ trunk/G1.txt (revision 4)
...
Patch as svn diff
between BASE revision and modified Working Copy
...
--- G1.txt (revision 4)
+++ G1.txt (working copy)
...
(---
strings in both cases contain revision, to which patch have to be applied)
For this easy case you have svn up
to SOURCE revision, svn patch
patch-file, in order to commit applied changes as new revision you must (with modified Working Copy) svn up
to HEAD revision, resolve all possible appeared conflicts and only after resolving all conflicts commit revision with changes
Another (somehow more usable way) may be: create branch from SOURCE revision, apply patch to WC of this branch, merge branch (with patch in it) back to mainline.
I'll prefer seconf way - less headache, less chances to commit mistakes