From 32f8fab0d6908535bfd796b655be73303926505c Mon Sep 17 00:00:00 2001
From: Francois-Rene Rideau <tunes@google.com>
Date: Fri, 14 Dec 2012 22:40:05 -0500
Subject: [PATCH] Better document :force and :force-not.

---
 doc/asdf.texinfo | 12 +++++++++---
 1 file changed, 9 insertions(+), 3 deletions(-)

diff --git a/doc/asdf.texinfo b/doc/asdf.texinfo
index 67566844..9f561e89 100644
--- a/doc/asdf.texinfo
+++ b/doc/asdf.texinfo
@@ -1461,15 +1461,21 @@ to invoke other operations on the system or its components:
 the new operations will be created
 with the same @var{initargs} as the original one.
 
-If @var{force} is @code{t}, then all systems
+If @var{force} is @code{:all}, then all systems
 are forced to be recompiled even if not modified since last compilation.
+If @var{force} is @code{t}, then only the system being loaded
+is forced to be recompiled even if not modified since last compilation,
+but other systems are not affected.
 If @var{force} is a list, then it specifies a list of systems that
 are forced to be recompiled even if not modified since last compilation.
-If @var{force-not} is @code{t}, then all systems
+If @var{force-not} is @code{:all}, then all systems
 are forced not to be recompiled even if modified since last compilation.
+If @var{force-not} is @code{t}, then only the system being loaded
+is forced not to be recompiled even if modified since last compilation,
+but other systems are not affected.
 If @var{force-not} is a list, then it specifies a list of systems that
 are forced not to be recompiled even if modified since last compilation.
-@var{force} takes precedences over @var{force-not};
+As of ASDF 2.26.22, @var{force-not} takes precedences over @var{force};
 both of them apply to systems that are dependencies and were already compiled.
 
 To see what @code{operate} would do, you can use:
-- 
GitLab