Tag Info

New answers tagged

0

While not a perfect solution, I use the following to grep through revisions of a specific file: for rev in `svn log FILE_TO_SEARCH | grep '^r[0-9][0-9]* ' | cut -f1 -d" "`; do svn cat -$rev FILE_TO_SEARCH 2>/dev/null | grep -q PATTERN_TO_FIND && echo $rev;done The output is a list of revision numbers of that file that contain the string.


0

VisualSVN Server 3.2 and newer includes an advanced web interface for Subversion repositories built with HTML5. The interface provides a history browser, syntax highlighting, inline diffs for changed files etc. Moreover, the web UI works out of the box; it does not require manual configuration.


0

Have you tried Apache's version? This can be either sourced in .bashrc or added to bash_completion https://svn.apache.org/repos/asf/subversion/trunk/tools/client-side/bash_completion


1

Apache provides a script that gives bash completion when the script is sourced in your .bashrc - it uses ~/.subversion/auth to provide the list for completion - it might be what you're looking for: https://svn.apache.org/repos/asf/subversion/trunk/tools/client-side/bash_completion


0

If you delete the ENTIRE working copy, including the top-level folder, you should have a checkout option. Checkout should be available in any directory where you don't already have a working copy. But you may not have actually needed to delete your working copy in the first place. If your working copy points to some parent of the reorganization, you only ...


0

Create the 3 directories under /home/project/trunk, and add that to source control. Then write a script that copies or export the relevant files where you want them to end up. Call this script every time you want to do a deploy.



Top 50 recent answers are included