On Sun, 2009-12-27 at 11:43 -0400, bulia byak wrote:
On Sun, Dec 27, 2009 at 8:35 AM, Arcadie M. Cracan <acracan@...400...> wrote:
I don't really know how I've managed to do this (bzr still seems a bit complicated to me) but I think the current revision is an outdated one. Please revert my today (Dec 27) commits.
Judging by http://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/files, we also lost a lot of recent revisions :(
Ted, can you please help us out? I'm having a deja vu :)
Yup. Fixed. Actually a similar problem to before, but now it is fixable :) I replayed some revisions so that they'd all appear in series, but that means they're committed by me. The originals are still in the history. This was only 4 revisions, so I thought that was much better than the way things were :)
What I like about SVN is that there, a revision is a revision. Once it's there, no one can delete it from history, accidentally or not. Isn't Bazaar operating on the same principle?
Yes, but what is immutable is the UUID of the version number, not the user friendly one. I love the userfriendly version numbers in Bazaar, but they aren't as solid as I may like :-/
What Bazaar is checking when you push to the branch is that you have a revision that has the current head revision as a parent. What it doesn't check is where that version is located in the tree. It could be on a branch (as in this case) and it doesn't check for that. So you can't delete data, but you can effectively change the layout of the tree.
Sorry I wasn't up on my e-mail this weekend.
--Ted