Re: Re: tsvn:logtemplate

There were a couple of reasons we made this change:

* SVN can walk the working copy more efficiently than we can
* SVN will essentially walk past the root of the WC.  So you can set these
properties on the root of your repository if you wanted, and they would
still be found.  In the old code, the properties had to exist on the part
of the repository you had checked out.

One side-effect I can imagine would be when svn:externals are used and you
have selected a path from an external.  I think the old code would have
walked back to the root of your working copy, but the SVN code would walk
back to the root of the external, because to SVN an external is a WC inside
of a WC.

I tend to think this behavior is right, but I can easily envision scenarios
where it will be a behavior change.

Mark


On Fri, Feb 21, 2014 at 10:23 AM, Stephen Elsemore <[email protected]>wrote:

>
> After Subclipse gets back the list of properties, it filters them to
> include only the closest for each property.  It determines this based on
> the lengths of the paths on which the property was found (assuming the
> longest path is the closest).  Looking at your command line output, does
> the longest "Properties on" or "Inherited properties on" path not
> correspond to the path on which Subclipse is picking up the
> tsvn:logtemplate property?  I still haven't been able to reproduce a
> problem.
>
> Thanks
>
> On Fri, Feb 21, 2014 at 5:25 AM, Lorenz <[email protected]> wrote:
>
>> Hi Stephen,
>>
>> finaly found the time to run some more test.
>>
>> Comparing the output of:
>>
>>    svn pg tsvn:logtemplate --show-inherited-props -v <path>
>>
>> against which template subclipse is picking up, it seems to me that
>> subclipse uses the last value "svn pg" lists as inherited.
>> --
>>
>> Lorenz
>>
>
>
>


-- 
Thanks

Mark Phippard
http://markphip.blogspot.com/

------------------------------------------------------
http://subclipse.tigris.org/ds/viewMessage.do?dsForumId=1047&dsMessageId=3073363

To unsubscribe from this discussion, e-mail: [[email protected]].