You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@subversion.apache.org by st...@apache.org on 2012/09/05 14:06:15 UTC

svn commit: r1381150 - /subversion/site/publish/faq.html

Author: stsp
Date: Wed Sep  5 12:06:14 2012
New Revision: 1381150

URL: http://svn.apache.org/viewvc?rev=1381150&view=rev
Log:
* publish/faq.html (removal): Document the svnsync history filtering trick.

Modified:
    subversion/site/publish/faq.html

Modified: subversion/site/publish/faq.html
URL: http://svn.apache.org/viewvc/subversion/site/publish/faq.html?rev=1381150&r1=1381149&r2=1381150&view=diff
==============================================================================
--- subversion/site/publish/faq.html (original)
+++ subversion/site/publish/faq.html Wed Sep  5 12:06:14 2012
@@ -1290,6 +1290,16 @@ repository, then pipe the dumpfile throu
 href="http://svnbook.red-bean.com/nightly/en/svn.reposadmin.html"
 >chapter 5</a> of the Subversion book for details about this.</p>
 
+<p>An alternative approach is to <a href="http://svnbook.red-bean.com/en/1.7/svn.reposadmin.maint.html#svn.reposadmin.maint.replication"
+>replicate the repository with <b>svnsync</b></a> after configuring
+<a href="http://svnbook.red-bean.com/en/1.7/svn.serverconfig.pathbasedauthz.html"
+>path-based authorization</a>
+rules that deny read access to any paths that need to be filtered from
+history. Unlike <b>svndumpfilter</b>, <b>svnsync</b> will automatically
+translate copy operations with an unreadable source path into normal
+additions, which is useful if history involving copy operations needs
+to be filtered.</p>
+
 </div>