No subject

of them (or part of) acting like an history and providing even
broader reuse.

Just throwing an idea here, I'm not fully convinced myself, but
it's often valuable to think about various implementations in the
design stage.

<snip/>

    bialix> So, I'm planning to implement in near future support
    bialix> for qbzr as described above.

Go ahead !

When I said to Garry that I want to provide as much support in
bzrlib that various clients may need, I never intended to forbid
said clients to implement their own solution.

Good designs are easier to reach when you have several working
implementations :-D

    bialix> If bzr-gtk developers think this approach could be
    bialix> interested for their tool, we can discuss how to
    bialix> share the code. If other parties interesting to talk
    bialix> about different variants or knows another problems
    bialix> I've not listed there, I'm open for constructive
    bialix> discussion.

I hope this helps.

    bialix> But in the end I'm planning to implement described
    bialix> above as good enough support for qbzr, even if it
    bialix> will be no ideal solution for everyone.

Again, go ahead !

       Vincent