; Mon, 27 Jun 2016 07:18:48 +0000 (UTC) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: svn commit: r1750285 - /subversion/site/publish/faq.html Date: Mon, 27 Jun 2016 07:18:48 -0000 To: commits@subversion.apache.org From: jcorvel@apache.org X-Mailer: svnmailer-1.0.9 Message-Id: <20160627071849.21F5A3A0096@svn01-us-west.apache.org> archived-at: Mon, 27 Jun 2016 07:18:57 -0000 Author: jcorvel Date: Mon Jun 27 07:18:48 2016 New Revision: 1750285 URL: http://svn.apache.org/viewvc?rev=1750285&view=rev Log: * site/publish/faq.html (readonly): Move this question to the BDB Questions under the Deprecated FAQ Modified: subversion/site/publish/faq.html Modified: subversion/site/publish/faq.html URL: http://svn.apache.org/viewvc/subversion/site/publish/faq.html?rev=1750285&r1=1750284&r2=1750285&view=diff ============================================================================== --- subversion/site/publish/faq.html (original) +++ subversion/site/publish/faq.html Mon Jun 27 07:18:48 2016 @@ -79,7 +79,6 @@ For older questions, see Should I store my repository / working copy on a NFS server?

How do I set repository permissions correctly?

Why do read-only operations still need repository write access?

How do I completely remove a file from the repository's history?

How do I change the log message for a revision after it's been committed?

@@ -1144,32 +1143,6 @@ access the repository.

Why do read-only operations still need repository -write access? - ¶ -

- -

Certain client operations are "read-only", like checkouts and -updates. From an access-control standpoint, Apache treats them as -such. But libsvn_fs (the repository filesystem API) still has to -write temporary data in order to produce tree-deltas. So the process -accessing the repository always requires both read and write -access to the Berkeley DB files in order to function.

- -

In particular, the repository responds to many "read-only" -operations by comparing two trees. One tree is the usually the HEAD -revision, and the other is often a temporary transaction-tree -- thus -the need for write access.

- -

This limitation only applies to the Berkeley DB backend; the FSFS backend does not exhibit this behaviour.

- -

How do I completely remove a file from the repository's history? @@ -4237,6 +4210,7 @@ Berkeley DB a repository is using?
After upgrading to Berkeley DB 4.3 or later, I'm seeing repository errors.
+
Why do read-only operations still need repository write access?

@@ -4707,10 +4681,35 @@ etc.) +

Why do read-only operations still need repository +write access? + ¶ +

+ +

Certain client operations are "read-only", like checkouts and +updates. From an access-control standpoint, Apache treats them as +such. But libsvn_fs (the repository filesystem API) still has to +write temporary data in order to produce tree-deltas. So the process +accessing the repository always requires both read and write +access to the Berkeley DB files in order to function.

+ +

In particular, the repository responds to many "read-only" +operations by comparing two trees. One tree is the usually the HEAD +revision, and the other is often a temporary transaction-tree -- thus +the need for write access.

+ +

This limitation only applies to the Berkeley DB backend; the FSFS backend does not exhibit this behaviour.

+ +

Why do read-only operations still need repository -write access? - ¶ -

How do I completely remove a file from the repository's history? @@ -4237,6 +4210,7 @@ Berkeley DB a repository is using? After upgrading to Berkeley DB 4.3 or later, I'm seeing repository errors. +Why do read-only operations still need repository write access?

Why do read-only operations still need repository +write access? + ¶ +

How do I completely remove a file from the repository's history? @@ -4237,6 +4210,7 @@ Berkeley DB a repository is using?
After upgrading to Berkeley DB 4.3 or later, I'm seeing repository errors.
+
Why do read-only operations still need repository write access?