philipp.marek@bmlv.gv.at wrote:
> Hyrum K. Wright wrote:
>
>> I have similar feelings. In working on some of the auditing code, I've
>> often thought "gee, if I could only tell if this copy is a branch or a
>> true copy." Having branches in directory hierarchy is very useful,
>> especially when browsing them using mod_dav_svn and my favorite web
>> browser. But the extra branch v. copy metadata would be useful.
>>
> How about just defining some extra property, that should be set to define some
> copy as a branch? Eg. "svn:branch-from" and some source
> (repository-root-relative) path, and revision, like this:
> svn:branch-from = /trunk:521
>
Oh ugh. Here's a square peg, I mean property, let's go find some round
holes for it.
> That could be set for existing branches cheaply, and newer clients would do that
> automatically - for a "svn branch" command, at least :-)
>
Are you quite sure you want to add another feature that causes the
client to do the server's job? Remember svn:externals and how useful
they are?
-- Brane
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Dec 15 03:23:37 2007