On Mon, Jul 16, 2012 at 02:11:10PM +0200, Bert Huijben wrote: > Open questions: > * 'svn:branch' or maybe 'svn:root'?
I'd prefer svn:branch but I don't care strongly. > * Which UI do/should we provide in 'svn' > svn cp --branch <PATH-OR-URL> URL > Performs a copy and makes sure there is a svn:branch property on the target > > svn mkdir --branch <PATH-OR-URL> > Creates a new branch I would favour a new 'svn branch' subcommand which is equivalent to 'svn copy' including a prop-add of 'svn:branch' at the copy target. > * How should we handle 'svn:branch' on multiple levels. E.g. on ^/trunk and > ^/trunk/projects/my? > [I don't see a problem with just allowing it as long as we usually only look > up to find the first ancestor] I would say that first svn:branch prop we find while traversing upwards wins. This would allow people to branch and merge within subtrees as they can do today.
