On Sat, 9 Apr 2022, at 13:54, Ted Felix wrote: > Interesting. svn should be really stable, so introducing a conflict > should require a monumental amount of effort.
I have a scripted setup for the various sites I host, that keeps a record of which revision and which version control system each site is currently checked out from. I tiredly ran the wrong admin command that (among other things) updated the wiki site to what it thought was the current version - this should have been a no-op, but its record was out of date, so it tried to update to an old version, resulting in conflicts against the files that had been changed locally. I do have most stuff scripted, but I managed to outwit the scripts this time. (The reason it had the wrong revision id recorded comes from another quirk of svn - that after you commit something, a subsequent svn info still shows the previous revision until you next do an svn update to sync with the repo. I think I understand why this is the case, but I also think it's possibly the single maddest feature in svn.) Chris _______________________________________________ Rosegarden-devel mailing list Rosegarden-devel@lists.sourceforge.net - use the link below to unsubscribe https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
