RE: RFC: Standardizing a 'svn:branch' (boolean) property
> -----Original Message-----
> From: C. Michael Pilato [mailto:cmpilato_at_collab.net]
> Sent: maandag 16 juli 2012 21:52
> To: Daniel Shahaf
> Cc: Bert Huijben; 'Branko Čibej'; dev_at_subversion.apache.org
> Subject: Re: RFC: Standardizing a 'svn:branch' (boolean) property
> On 07/16/2012 03:41 PM, Daniel Shahaf wrote:
> > Bert Huijben wrote on Mon, Jul 16, 2012 at 19:51:59 +0200:
> >> 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.
> Huh? Most trunks won't have mergeinfo on them unless they've been the
> recipient of a merge from elsewhere.
Just checking a few real world repositories and yes, trunk doesn't have svn:mergeinfo in my 'normal' usecases.
And I think this would certainly apply to about every repository where one is experimenting with the tools to find out whether they want to use it or not.
Received on 2012-07-16 22:52:16 CEST
This is an archived mail posted to the Subversion Dev