[RFC] new format 1.12 (1.11?) enabling EOL & filtered views
andrew at operationaldynamics.com
Tue Dec 16 01:03:26 GMT 2008
On Mon, 2008-12-15 at 09:05 -0600, John Arbash Meinel wrote:
> Upgrading non-rr to rr is a hard process because we re-serialize
> everything, and commits to rr are not allowed in non-rr repositories, so
> it introduces far more difficulties. Simply wanting to experiment with
> a new WT feature should not prevent you from merging your changes back
> into bzr.dev.
So upgrade bzr.dev to a rich-root format?
Why you are worrying about hackers working on the mainline branch who
using a version of Bazaar that not already capable of supporting
rich-root is a bit of a mystery (actually, why you'd want anyone hacking
on Bazaar who is not at least using the most recent release [let alone
bzr.dev itself] is mind boggling, but anyway).
This is just more of the "it's going to hurt someday, and as long as you
keep putting it off, we're going to keep having conversations about how
it's going to hurt some day". There should be a recursive acronym for
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 197 bytes
Desc: This is a digitally signed message part
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20081216/adaf691b/attachment.pgp
More information about the bazaar