Editing Talk:Vision For Direction: The Otiose Objectives

As Robert notes, you can do:svn merge -c-Xwhere X is the single reivison the change happened.  the -c is to specify a single reivison, and leading the reivison with a '-' indicates it should be reversed.Ash, that's just wrong!  The whole point of reivison control is that it should maintain a complete history of the changes to your code.  The metadata associated with each change (the log message, for example) is invaluable in explaining *why* something was done, or why it was wrong.  It's one of the major problems I have with most dvcs (git, darcs, etc) solutions; it becomes possible to lose reivisons and revise history.
Current revision		Your text
Line 1:		Line 1:
-	~~That~~'s ~~an epxret answer~~ to ~~an interesting question~~	+	As Robert notes, you can do:svn merge -c-Xwhere X is the single reivison the change happened. the -c is to specify a single reivison, and leading the reivison with a '-' indicates it should be reversed.Ash, that's just wrong! The whole point of reivison control is that it should maintain a complete history of the changes to your code. The metadata associated with each change (the log message, for example) is invaluable in explaining why something was done, or why it was wrong. It's one of the major problems I have with most dvcs (git, darcs, etc) solutions; it becomes possible to lose reivisons and revise history.