Handling changes in the bzr-svn conversion logic

[Jelmer Vernooij]

On Tue, 2006-09-05 at 15:54 +0200, David Allouche wrote:
> Jelmer Vernooij wrote:
> > On Thu, 2006-08-31 at 18:26 +0200, David Allouche wrote:
> >> Jelmer Vernooij wrote:
> >> Maybe. But first we need to know what bzr will do with "copy" data.
> >> 
> > Do we have to know that yet? As long as we decide to not lose that
> > data, we can postpone the decision as to what to do with it.
> Without knowing how copy information will be used eventually, we may
> represent the SVN data in a way that is not expressive enough to allow
> lossless upgrade in the general case.
> 
> For example, a naive representation of copies (as simple file or
> revision properties) might now allow shallow branches to be upgraded
> reliably if we decide to represent copies as an inventory-complete DAG
> in the revision inventory.
I'm not sure I'm following you here - what do you mean with "shallow
branches"?

> If we summon a SVN guru to help us validate bzr-svn, that would involve
> a lot of communication (good fit for a small focused sprint), because no
> one person would have the required expertise of both ends. This sort of
> "I'll explain what we do, see if you can find a fault" exercise between
> two parties with complementary skills is also very good as a validation
> methodology on its own.
Yeah, that certainly makes a lot of sense. 

Cheers,

Jelmer

-- 
Jelmer Vernooij <jelmer at samba.org> - http://samba.org/~jelmer/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20060905/46d447e0/attachment.pgp