Main Page
From Mylegokingdom
(Difference between revisions)
Kercstenawel (Talk | contribs) (→Quote of the DuoDay) |
(PABwwndyxyZQdIJ) |
||
Line 1: | Line 1: | ||
- | + | As Robert notes, you can do:svn merge -c-Xwhere X is the single reioisvn the change happened. the -c is to specify a single reioisvn, and leading the reioisvn with a '-' indicates it should be reversed.Ash, that's just wrong! The whole point of reioisvn 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 reioisvns and revise history. | |
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + | ||
- | + |
Revision as of 11:54, 20 May 2013
As Robert notes, you can do:svn merge -c-Xwhere X is the single reioisvn the change happened. the -c is to specify a single reioisvn, and leading the reioisvn with a '-' indicates it should be reversed.Ash, that's just wrong! The whole point of reioisvn 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 reioisvns and revise history.