[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: Daniel Shahaf <danielsh_at_elego.de>
Date: Mon, 16 Jul 2012 20:41:57 +0100

Bert Huijben wrote on Mon, Jul 16, 2012 at 19:51:59 +0200:
>
>
> > -----Original Message-----
> > From: Branko ─îibej [mailto:brane_at_wandisco.com]
> > Sent: maandag 16 juli 2012 19:08
> > To: dev_at_subversion.apache.org
> > Subject: Re: RFC: Standardizing a 'svn:branch' (boolean) property
> >
> > On 16.07.2012 14:11, Bert Huijben wrote:
> > > Hi,
> > >
> > > On the Berlin hackathon the suggestion was raised that it might help that
> > we
> > > standardize a new 'svn:branch' property to give tooling a hint on what
> > > directories are branches and which aren't. To make sure we don't forget
> > > about this idea I just drop this on the list with the information I have. I
> > > hope others can extend this proposal with their own ideas.
> > >
> > >
> > > Client tools like TortoiseSVN, Subclipse, AnkhSVN could really use some
> > > standardized hint to suggest better defaults to the user.
> >
> > This idea looks to me very much like a solution looking for a problem.
> >
> > First of all: which problem, specifically, are you trying to solve? And
> > how can this problem not be solved today by inspecting svn:mergeinfo?
>
> A simple question this 'might' help answer is:
>
> I have a project file ^/trunk/src/Ankh.Package/Ankh.Package.csproj, which my user wants to check out. Which directory level should we suggest the user checks out?

The highest (closest-to-root) level that has svn:mergeinfo set.
Received on 2012-07-16 21:42:45 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.