Ok, so this kind of bugs me. I have a list of revisions and when I try to make a previous revision current, it copies that revision and sets it current. Great, now I have 2 copies of the same revision. All I wanted to do was revert back to a previous one. Hmmm...
Now, I can see the benefit to creating the copy, but usability wise, this is not the expected result. If I'm reverting back to an older revision why is a copy of that being made? It doesn't make sense to me. Do other revision systems do this? I haven't encountered any like this.
A patch to change this is pretty trivial, but I'd like to hear other people's thoughts on this system. If people agree, I'll come up with a patch to fix this.
Comments
Comment #1
killes@www.drop.org commentedIn fact, the behaviour was initially to not create a copy. Some people explained that the expected behaviour (probably from some wiki software) would be to create copies. Thus I chaned it. :p
Comment #2
m3avrck commentedAh ok, well I still thing the copies is part is "non-intuitive". Can you guys post more feedback? I'd like to see it changed if people agree or leave it if the majority likes it that way, cheers!
Comment #3
killes@www.drop.org commentedsome comments can be found here:
http://drupal.org/node/30329
http://drupal.org/node/30098
Comment #4
m3avrck commentedkilles, I see now. Perhaps I was a bit haste in making my comment here :-) I see now why the copy is useful and I'll close this thread appropriately :-)