subversion-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache subversion Wiki <comm...@subversion.apache.org>
Subject [Subversion Wiki] Update of "MultiLayerMoves" by StefanSperling
Date Wed, 08 Feb 2012 18:18:36 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Subversion Wiki" for change notification.

The "MultiLayerMoves" page has been changed by StefanSperling:
http://wiki.apache.org/subversion/MultiLayerMoves?action=diff&rev1=14&rev2=15

Comment:
make gstein more happy

  
  This would involve rewriting the moves inside A when A is moved to B.
  
- The DB state should be independent of the order of moves. We not care about the order in
which moves were performed, only about the resulting state. So the end result should be the
same for both "A -> B; A/F -> A/G;" and "A/F -> A/G; A -> B";
+ The DB state should be independent of the order of moves. We not care about the order in
which moves were performed, only about the resulting state. So the end result should be the
same for both "A -> B; B/F -> B/G;" and "A/F -> A/G; A -> B";
  
- '''gstein''': stop saying that. You cannot move A -> B '''and then''' move A/F ->
A/G. The second move is impossible because A/F does not exist. Please stop using this example
when talking about this stuff. It is repeated above and below and whatever. Gah.
- 
- The first case, A -> B; A/F -> A/G, is shown above.
+ The first case, A -> B; B/F -> B/G, is shown above.
  
  For the second sequence we would need transitions between the following states:
  

Mime
View raw message