On Dec 6, 2007 3:17 AM, <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
>
> That could be set for existing branches cheaply, and newer clients would do that
> automatically - for a "svn branch" command, at least :-)
>
>
> Regards,
>
> Phil
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: dev-help@subversion.tigris.org
>
>
I really like this idea! Existing clients and such could take the
info or leave it. I could also see how it might make some graphing
clients perform a little better, if not for showing all the merges
(which it can't do right now anyway) at least enough to show all the
branch points. Plus it would not take much to implement but has
potential for being very useful.
Troy
--
"Beware of spyware. If you can, use the Firefox browser." - USA Today
Download now at http://getfirefox.com
Registered Linux User #354814 ( http://counter.li.org/)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Dec 8 19:13:38 2007