1.7.x configure script should suggest running get-deps.sh when appropriate

2011-07-24 Thread Joel N. Weber II
At least in 1.7.0-beta2, if you run ./configure without the appropriate dependencies available, you get an error message like the below. It would be helpful if this message could be adjusted to recommend running ./get-deps.sh configure: Apache Portable Runtime (APR) library configuration checkin

is_wc function in svnmerge.py vs svn 1.7

2011-07-24 Thread Joel N. Weber II
https://svn.apache.org/repos/asf/subversion/trunk/contrib/client-side/svnmerge/svnmerge.py contains this function: def is_wc(dir): """Check if a directory is a working copy.""" return os.path.isdir(os.path.join(dir, ".svn")) or \ os.path.isdir(os.path.join(dir, "_svn")) which

Re: svn log --diff --depth=empty

2011-05-15 Thread Joel N. Weber II
> > Would it be possible for svn log --diff to accept the same --depth > > argument that svn diff does? An svn client I built from trunk last > > week does not recognize --depth in conjuction with svn log --diff > > It now does as of r1100830. Let me know if it works as expected. > Thanks for the

network data compression level by client IP

2011-05-08 Thread Joel N. Weber II
http://subversion.apache.org/docs/release-notes/1.7 discusses how to adjust the network data compression level as a global setting. Is there a mechanism by which compression can be turned off for clients whose IP address implies they are on the same LAN as the server, but turned on for clients on

svn log --diff --depth=empty

2011-05-08 Thread Joel N. Weber II
The --diff option expected to be added to svn log in svn 1.7 looks useful. Would it be possible for svn log --diff to accept the same --depth argument that svn diff does? An svn client I built from trunk last week does not recognize --depth in conjuction with svn log --diff

svnmerge.py parsing svn:mergeinfo

2011-04-24 Thread Joel N. Weber II
I have been exploring whether it is possible to modify svnmerge.py to parse svn:mergeinfo instead of svnmerge-integrated. I am wondering if anyone else has been down this path and has any insight to add as to why the svnmerge.py shipped with Subversion still relies on svnmerge-integrated, instead