rsvn - remote svn - run subversion commands on the file server if possible
rsvn ANY_SVN_COMMAND rsvn update rsvn --test
When possible, run the svn command on the file server where it does not have to wait for NFS. Otherwise run svn as usual. Some SVN commands will always run locally, either for "safety" or because there is no benefit of running on the file server (svn log).
The commands that will be sent to the file server by default are these (and their abbreviations):
add checkout cleanup diff merge resolved revert status switch update
Why is commit not run remotely? Because it will either start an editor, which won't always work through noninteractive SSH, or you might use -m "FOO BAR" and the shell's quoting gets all screwed up. It would be good to figure out how to solve these problems, and add "commit" to the list.
Print debug messages.
Displays this message and program version and exits.
Force a command to be run locally, even if normally it could be run on the file server.
Attempt to run the command on the file server, even if normally it would not be.
Print debug messages and DON'T actually execute the svn command.
Displays program version and remote svn version.
The command to use in place of "ssh" to login to remote systems. Used only if RSVN_SSH not set.
The command to use in place of "ssh" to login to remote systems.
Perl regular expression containing servers that can be rsvn'ed into, defaults to '.*'. Generally any file server which supports "ssh" and has NFS mounts matching the localhost can be specified here. Network Attached Storage (NAS) boxes such as Network Appliance servers must be excluded (by not including them in the regexp).
Copyright 2006-2010 by Bryce Denney and Wilson Snyder. This package is free software; you can redistribute it and/or modify it under the terms of either the GNU Lesser General Public License or the Perl Artistic License.
Bryce Denney <email@example.com>, Wilson Snyder <firstname.lastname@example.org>