On Wed, 2005-08-31 at 15:25 +1200, Martin Langhoff wrote: > On 8/31/05, Robert Collins <firstname.lastname@example.org> wrote: > > for the record, to avoid other folk getting confused - bzr isn't a > > 'patch orientated SCM'. bzr's design incorporates elements from all of > > the VCS systems around when the project was started (and updated since > > then) - its not derived from GNU Arch any more or less than its derived > > from monotone or subversion. > > Fair enough... except that it is being promised as the natural upgrade > path for tla/baz users. I don't claim to understand the architectural > decisions in bzr, but it is a pretty serious constraint. It forces bzr > to support the core assumptions of the Arch model. Not at all. I'll reply to madduck with more stuff on the design internals tomorrow. But as for being forced to support the core assumptions of the arch model - bah. bzr will support upgrades by converting the data from the arch archives to individual bzr branches. These branches are not able to be converted back to Arch archives - its a one way trapdoor. The presence of the trapdoor is what lets Bazaar-NG not support the core assumptions of the Arch model. Aaron Bentley has already written a baz2bzr tool and I'll be knocking the edges of that in the next month and a half. Rob -- GPG key available at: <http://www.robertcollins.net/keys.txt>.
Description: This is a digitally signed message part