On Tue, 2008-11-25 at 19:31 -0400, bulia byak wrote:
On Mon, Nov 24, 2008 at 11:55 AM, Maximilian Albert
So, are you seeing any revisions between 19921 and 20226 in current SVN trunk? Strangely, in my fresh SVN checkout, svn log doesn't show me revision 20232 which you mentioned either...
Actually, I do not. So it's even worse than I thought. It seems to have caused information loss in the main SVN repository!
No, there is no information loss.
In my bash history, I have this recent commit:
svn commit -m "patch 188849 by RM for better pencil interpolation taking into account all points" pencil-context.h pencil-context.cpp
but at
http://inkscape.svn.sourceforge.net/viewvc/inkscape/inkscape/trunk/src/penci...
there's no such comment listed.
The revision is here:
http://inkscape.svn.sourceforge.net/viewvc/inkscape?view=rev&revision=20...
This is very bad. We now have some recent bugs that would benefit from searching in SVN history, but the breakage makes this impossible. Please, Ted, make sure this thing never happens again. I would even suggest not using the tool which is capable of wreaking such havoc (I'm pretty sure plain SVN client cannot ever delete revisions from the repository!)
What has happened is the history path for the individual files doesn't directly include a set in the middle. The key version to look at is this one:
http://inkscape.svn.sourceforge.net/viewvc/inkscape?view=rev&revision=20...
What's important to notice is the comments on "inkscape/trunk":
(Copied from inkscape/trunk, r19921)
Basically it deleted "trunk" and copied the "trunk" from revision 19921. So the version history from 19921 to 20225 was collapsed into version 20226. This is similar to using a distributed branch in SVK, GIT or Bazaar and then merging it in. The entire history of that branch is collapsed into a single version.
Now, I'm not saying that in anyway this is good. But it isn't information loss or anything as drastic as that, and I've taken measures on my end to ensure it doesn't happen.
--Ted