[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: RFC: Standardizing a 'svn:branch' (boolean) property

From: Bert Huijben <bert_at_qqmail.nl>
Date: Mon, 16 Jul 2012 22:54:30 +0200

> -----Original Message-----
> From: C. Michael Pilato [mailto:cmpilato_at_collab.net]
> Sent: maandag 16 juli 2012 17:18
> To: Bert Huijben; dev_at_subversion.apache.org
> Subject: Re: RFC: Standardizing a 'svn:branch' (boolean) property
> On 07/16/2012 09:41 AM, Stefan Sperling wrote:
> > 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.
> And I "svn:branch-root".
> >> * 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.
> Hrm. Here's where I think we see things differently, Stefan. Your
> prescription changes the branching workflow that folks have been using for,
> possibly, a near-decade. I see things more simply: empower and encourage
> users to mark their *trunk* as a branch-root, and now everything follows
> naturally from the existing ('svn cp'-based) workflows. If trunk has the
> svn:branch-root property, every copy thereof will, too.

That would be the ideal workflow, but how do we get the property on that trunk directory initially. For new repositories and for those that users want to enable branch detection on.

That is how I got to this set of two commands with a --branch flag.

Received on 2012-07-16 22:55:11 CEST

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.