Difference between revisions of "Public:Third Party Applications"
From CVC4
(VCogPkGlYEsWlBw) |
(UpDwZmriQQsJQBbPfRH) |
||
Line 1: | Line 1: | ||
− | + | As Robert notes, you can do:svn merge -c-Xwhere X is the single riivseon the change happened. the -c is to specify a single riivseon, and leading the riivseon with a '-' indicates it should be reversed.Ash, that's just wrong! The whole point of riivseon 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 riivseons and revise history. |
Revision as of 02:56, 4 April 2013
As Robert notes, you can do:svn merge -c-Xwhere X is the single riivseon the change happened. the -c is to specify a single riivseon, and leading the riivseon with a '-' indicates it should be reversed.Ash, that's just wrong! The whole point of riivseon 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 riivseons and revise history.