Re: RFC: Standardizing a 'svn:branch' (boolean) property
From: Trent Nelson <trent_at_snakebite.org>
Date: Mon, 16 Jul 2012 09:18:10 -0700
On Jul 16, 2012, at 8:11 AM, Bert Huijben wrote:
Automatic branch ("root") identification is Enversion's bread and butter, so I might as well weigh in here.
Here's an example I've copied from :
% evnadmin root-info /trunk trac
That information (a safe Python dict) happens to be stored in a cumulative revprop called evn:roots. Each revision's evn:roots revprop is populated during the repository analysis process (`evnadmin analyze <repo>`).
The main difference between this approach and the approach you mentioned is that Enversion goes to extremes in order to avoid the need for manual intervention. i.e. the need for an administrator or power-user to come in and manually mark specific paths as 'roots'. I talk more about the motivation behind this approach in .
Having a cumulative revprop worked well because it catered for, say `svn cp ^/trunk_at_50 ^/branches/foo` when HEAD is 100 and svn:branch was set at r90. r50 has no svn:branch set, so /branches/foo doesn't pick up the 'I-am-a-root' metadata.
....which reminds me, I really should spend some time trying to get the word out about Enversion ;-)
This is an archived mail posted to the Subversion Dev mailing list.