Comments on: How to roll back commits to an earlier version of a repository in SVN http://www.rustyrazorblade.com/2007/04/how-to-roll-back-commits-to-an-earlier-version-of-a-repository-in-svn/ Tech Thoughts, Mostly on LAMP - by Jon Haddad Mon, 23 Jan 2012 09:03:48 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: animal http://www.rustyrazorblade.com/2007/04/how-to-roll-back-commits-to-an-earlier-version-of-a-repository-in-svn/comment-page-1/#comment-51379 animal Fri, 16 Jul 2010 22:00:23 +0000 http://www.rustyrazorblade.com/index.php/2007/04/06/how-to-roll-back-commits-to-an-earlier-version-of-a-repository-in-svn/#comment-51379 Thanks, i found it through google search on "svn rollback" too. Great. Thanks, i found it through google search on “svn rollback” too.

Great.

]]> By: Adam Loving http://www.rustyrazorblade.com/2007/04/how-to-roll-back-commits-to-an-earlier-version-of-a-repository-in-svn/comment-page-1/#comment-33122 Adam Loving Fri, 19 Dec 2008 22:23:23 +0000 http://www.rustyrazorblade.com/index.php/2007/04/06/how-to-roll-back-commits-to-an-earlier-version-of-a-repository-in-svn/#comment-33122 Thanks alot Tom, I found this searching for "svn rollback" - which makes more sense then "reverse merge". cheers. Thanks alot Tom, I found this searching for “svn rollback” – which makes more sense then “reverse merge”. cheers.

]]> By: Tom http://www.rustyrazorblade.com/2007/04/how-to-roll-back-commits-to-an-earlier-version-of-a-repository-in-svn/comment-page-1/#comment-18767 Tom Tue, 15 Apr 2008 15:58:48 +0000 http://www.rustyrazorblade.com/index.php/2007/04/06/how-to-roll-back-commits-to-an-earlier-version-of-a-repository-in-svn/#comment-18767 Thanks for the info! I couldn't get to the SVN nightly docs(broken link) but found this: http://svnbook.red-bean.com/en/1.0/ch04s04.html#svn-ch-4-sect-4.2 Thanks for the info! I couldn’t get to the SVN nightly docs(broken link) but found this:
http://svnbook.red-bean.com/en/1.0/ch04s04.html#svn-ch-4-sect-4.2

]]> By: jon http://www.rustyrazorblade.com/2007/04/how-to-roll-back-commits-to-an-earlier-version-of-a-repository-in-svn/comment-page-1/#comment-14524 jon Mon, 14 Jan 2008 17:41:17 +0000 http://www.rustyrazorblade.com/index.php/2007/04/06/how-to-roll-back-commits-to-an-earlier-version-of-a-repository-in-svn/#comment-14524 From svn help merge: The '-c M' option is equivalent to '-r N:M' where N = M-1. Using '-c -M' does the reverse: '-r M:N' where N = M-1. svn --version svn, version 1.4.5 (r25188) I think you can use -r HEAD:OLD_REVISION_NUMBER if you're using an old version. From svn help merge:

The ‘-c M’ option is equivalent to ‘-r N:M’ where N = M-1.
Using ‘-c -M’ does the reverse: ‘-r M:N’ where N = M-1.

svn –version
svn, version 1.4.5 (r25188)

I think you can use -r HEAD:OLD_REVISION_NUMBER if you’re using an old version.

]]> By: Stewart http://www.rustyrazorblade.com/2007/04/how-to-roll-back-commits-to-an-earlier-version-of-a-repository-in-svn/comment-page-1/#comment-14469 Stewart Fri, 11 Jan 2008 11:21:43 +0000 http://www.rustyrazorblade.com/index.php/2007/04/06/how-to-roll-back-commits-to-an-earlier-version-of-a-repository-in-svn/#comment-14469 I don't get what the '-c' option is, that you've put on the svn merge command. When I try this I get: svn: invalid option character: c Typing 'svn help merge' gives: merge: Apply the differences between two sources to a working copy path. usage: 1. merge sourceURL1[@N] sourceURL2[@M] [WCPATH] 2. merge sourceWCPATH1@N sourceWCPATH2@M [WCPATH] 3. merge -r N:M SOURCE[@REV] [WCPATH] 1. In the first form, the source URLs are specified at revisions N and M. These are the two sources to be compared. The revisions default to HEAD if omitted. 2. In the second form, the URLs corresponding to the source working copy paths define the sources to be compared. The revisions must be specified. 3. In the third form, SOURCE can be a URL, or working copy item in which case the corresponding URL is used. This URL in revision REV is compared as it existed between revisions N and M. If REV is not specified, HEAD is assumed. WCPATH is the working copy path that will receive the changes. If WCPATH is omitted, a default value of '.' is assumed, unless the sources have identical basenames that match a file within '.': in which case, the differences will be applied to that file. Valid options: -r [--revision] arg : ARG (some commands also take ARG1:ARG2 range) A revision argument can be one of: NUMBER revision number "{" DATE "}" revision at start of the date "HEAD" latest in repository "BASE" base rev of item's working copy "COMMITTED" last commit at or before BASE "PREV" revision just before COMMITTED -N [--non-recursive] : operate on single directory only -q [--quiet] : print as little as possible --force : force operation to run --dry-run : try operation but make no changes --diff3-cmd arg : use ARG as merge command --ignore-ancestry : ignore ancestry when calculating merges --username arg : specify a username ARG --password arg : specify a password ARG --no-auth-cache : do not cache authentication tokens --non-interactive : do no interactive prompting --config-dir arg : read user configuration files from directory ARG I don’t get what the ‘-c’ option is, that you’ve put on the svn merge command. When I try this I get:
svn: invalid option character: c

Typing ‘svn help merge’ gives:
merge: Apply the differences between two sources to a working copy path.
usage: 1. merge sourceURL1[@N] sourceURL2[@M] [WCPATH]
2. merge sourceWCPATH1@N sourceWCPATH2@M [WCPATH]
3. merge -r N:M SOURCE[@REV] [WCPATH]

1. In the first form, the source URLs are specified at revisions
N and M. These are the two sources to be compared. The revisions
default to HEAD if omitted.

2. In the second form, the URLs corresponding to the source working
copy paths define the sources to be compared. The revisions must
be specified.

3. In the third form, SOURCE can be a URL, or working copy item
in which case the corresponding URL is used. This URL in
revision REV is compared as it existed between revisions N and
M. If REV is not specified, HEAD is assumed.

WCPATH is the working copy path that will receive the changes.
If WCPATH is omitted, a default value of ‘.’ is assumed, unless
the sources have identical basenames that match a file within ‘.’:
in which case, the differences will be applied to that file.

Valid options:
-r [--revision] arg : ARG (some commands also take ARG1:ARG2 range)
A revision argument can be one of:
NUMBER revision number
“{” DATE “}” revision at start of the date
“HEAD” latest in repository
“BASE” base rev of item’s working copy
“COMMITTED” last commit at or before BASE
“PREV” revision just before COMMITTED
-N [--non-recursive] : operate on single directory only
-q [--quiet] : print as little as possible
–force : force operation to run
–dry-run : try operation but make no changes
–diff3-cmd arg : use ARG as merge command
–ignore-ancestry : ignore ancestry when calculating merges
–username arg : specify a username ARG
–password arg : specify a password ARG
–no-auth-cache : do not cache authentication tokens
–non-interactive : do no interactive prompting
–config-dir arg : read user configuration files from directory ARG

]]> By: Aman http://www.rustyrazorblade.com/2007/04/how-to-roll-back-commits-to-an-earlier-version-of-a-repository-in-svn/comment-page-1/#comment-12720 Aman Fri, 30 Nov 2007 11:16:06 +0000 http://www.rustyrazorblade.com/index.php/2007/04/06/how-to-roll-back-commits-to-an-earlier-version-of-a-repository-in-svn/#comment-12720 Thanks for the post. I was also looking for this information. Best wishes. Thanks for the post. I was also looking for this information.

Best wishes.

]]>