Are svn properties in bzr-svn important?

[Aaron Bentley]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Jelmer Vernooij wrote:
> On Thu, 2007-07-12 at 09:37 -0400, Aaron Bentley wrote:
>> Jelmer Vernooij wrote:
> I can't set the contents of this property for one
> specific revision, I can only set it as part of a change. 

I don't understand what you mean here: surely each revision is a change.

> In the current scheme, bzr:merge contains anything that's ever been
> merged. When looking for the merged revisions, I look for changes to
> bzr:merge. 
> 
> If I would keep this property limited to one line, that would have the
> following disadvantages:
> 
>  * get_ancestry() would significantly slower. This should be acceptable
> I think

You could cache this data.  Significantly, you can cache it on the
client side.  But you may even be able to cache it server-side.

Say you create a fake revision 6, with an "ancestry" property.  Since
revision properties in svn are mutable, you can use that property of
revision 6 to track data about all revisions in the system.

Also, I'll remind you that as part of the performance drive, we are
working on supporting operations using partial histories.  So
get_ancestry should ultimately never be used.  Only get_parents.

>  * Looking at bzr:merge for a revision X will contain one line Y and
> suggest that Y was merged in X, whereas it was perhaps actually merged
> in X-2.

Why wouldn't it be marked in X-2, then?

> I could use Subversion revision properties for bzr:merge, but they can
> be configured to be modifiable afterwards and need to be enabled in the
> repository configuration.

Oh, are these file properties?

Aaron
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGljer0F+nu1YWqI0RAmc9AJ9OjaGQ7U/H+F9gyLw1LbOFTRLDLgCcDz1p
wGBeFVLpLAd/WOuDysWkwAs=
=o9RY
-----END PGP SIGNATURE-----