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

Re: svn commit: r1037738 - "Summary of updates"

From: C. Michael Pilato <cmpilato_at_collab.net>
Date: Mon, 29 Nov 2010 14:17:13 -0500

On 11/26/2010 01:01 AM, Daniel Shahaf wrote:
> Thanks for this :-). It works as expected when the current directory is
> entered by its name, but not when it's entered through a symlink:
> [[[
> % cd /tmp
> % ln -s wc1 wcalias
> % cd wc1
> % $svn up /tmp/wc1/trunk/iota
> Updating 'trunk/iota' ...
> % cd /tmp/wcalias
> % $svn up /tmp/wc1/trunk/iota11D
> Updating 'trunk/iota' ...
> % $svn up /tmp/wcalias/trunk/iota
> Updating '/tmp/wcalias/trunk/iota' ...
> ]]]
> Ideally, the last output would have used the relative path 'trunk/iota',
> too. However, I'm not sure how to easily solve that --- is it as easy
> as calling some "resolve symlinks" function on the absolute-cwd string?

Do we have a "resolve symlinks" function?

>> I'm wondering what would happen -- that is, how
>> much chaos would ensue -- if we changed subversion/svn/notify.c:notify() to,
>> in the case where n->path is not a URL, always first convert n->path to an
>> absolute path before doing the prefix removal stuff.
> What chaos could ensure? Just N+1 test expectations, or something more?

Not necessarily anything more. I mean, test expectations reflect, to some
degree, the expectations of Subversion users wrapping the command-line for
output parsing. I sense we're cool with some sane amount of change in that
output so as to make the tool better without completely breaking the world.
 :-) ('Cause if we're cool with breaking the world, I have quite a few
changes in mind that I'd like to make to the output!)

C. Michael Pilato <cmpilato_at_collab.net>
CollabNet   <>   www.collab.net   <>   Distributed Development On Demand
Received on 2010-11-29 20:17:54 CET

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.