[Emacs-diffs] master 53830c6: Remove obsolete vc-mistrust-permissions doc

[Paul Eggert]

branch: master
commit 53830c6336b52d58c315c7e11405181e01ee9a53
Author: Paul Eggert <address@hidden>
Commit: Paul Eggert <address@hidden>

    Remove obsolete vc-mistrust-permissions doc
    
    * doc/emacs/vc1-xtra.texi (RCS and SCCS): Remove documentation
    for vc-mistrust-permissions, which no longer exists.
---
 doc/emacs/vc1-xtra.texi | 15 +--------------
 1 file changed, 1 insertion(+), 14 deletions(-)

diff --git a/doc/emacs/vc1-xtra.texi b/doc/emacs/vc1-xtra.texi
index 8e5c5d5..58e4de0 100644
--- a/doc/emacs/vc1-xtra.texi
+++ b/doc/emacs/vc1-xtra.texi
@@ -347,22 +347,9 @@ status by setting @code{vc-consult-headers} to @code{nil}. 
 VC then
 always uses the file permissions (if it is supposed to trust them), or
 else checks the master file.
 
address@hidden vc-mistrust-permissions
-  You can specify the criterion for whether to trust the file
-permissions by setting the variable @code{vc-mistrust-permissions}.
-Its value can be @code{t} (always mistrust the file permissions and
-check the master file), @code{nil} (always trust the file
-permissions), or a function of one argument which makes the decision.
-The argument is the directory name of the @file{RCS} subdirectory.  A
address@hidden value from the function says to mistrust the file
-permissions.  If you find that the file permissions of work files are
-changed erroneously, set @code{vc-mistrust-permissions} to @code{t}.
-Then VC always checks the master file to determine the file's status.
-
   VC determines the version control state of files under SCCS much as
 with address@hidden  It does not consider SCCS version headers, though.  Thus,
-the variable @code{vc-mistrust-permissions} affects SCCS use, but
address@hidden does not.
+the variable @code{vc-consult-headers} does not affect SCCS use.
 
 @node CVS Options
 @subsubsection Options specific for CVS