On Mon, Dec 28, 2009 at 12:28 PM, bulia byak <buliabyak@...400...> wrote:
On Sun, Dec 27, 2009 at 9:22 PM, Jon Cruz <jon@...18...> wrote:
And after I pulled, all of my recent changes seem intact. So we are good.
Actually we're not good at all. For example
http://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/revision/8859#src/w...
lumps together my latest change to this file with a lot of other changes, all under rev 8859 ascribed to Arcadie Cracan.
Now, the basic purpose of any revision control system is exactly this: to record/show who changed what and in what order. If it fails in this basic purpose - if it is SO easy to break it - I seriously doubt it is fit for serious use.
Missing revisions are a really, really bad thing. The black hole Ted created in our SVN was felt for months - even though no files were lost, only records of revisions. Now we have a very similar thing happen, perhaps even exactly the same (Ted was using a bzr client for svn, as far as I remember), just weeks after we switched to a new system. I request that those in charge please investigate some ways to AUTOMATICALLY prevent this thing from happening (e.g. by banning branches unless approved by moderator). A wiki page is not enough.