Signed-off-by: Teng Long <dyroneteng@xxxxxxxxx>
---
Documentation/technical/packfile-uri.txt | 18 ++++++++++++------
1 file changed, 12 insertions(+), 6 deletions(-)
diff --git a/Documentation/technical/packfile-uri.txt b/Documentation/technical/packfile-uri.txt
index c3e4873956..bf5939cb8d 100644
--- a/Documentation/technical/packfile-uri.txt
+++ b/Documentation/technical/packfile-uri.txt
@@ -39,12 +39,18 @@ server to be configured by one or more entries with the format:
uploadpack.excludeobject=<object-hash> <pack-hash> <uri>
-Value <object-hash> is the key of entry, and the object type can be a blob,
-tree, or commit. The exclusion of tree and commit is recursive by default,
-which means that when a tree or commit object is excluded, the object itself
-and all reachable objects of the object will be excluded recursively. Whenever
-the list of objects to be sent is assembled, all such objects are excluded,
-replaced with URIs.
+Value <object-hash> is the key of entry, and the object type can be blob, tree,
+commit, or tag. When an object is configured with `uploadpack.excludeobject` which
+means that whenever the list of objects to be sent is assembled, the object (also
+include the related objects in some cases, the following will introduce) will be
+excluded, replaced with URIS. The mechanism for exclusion is as follows:
+
+ * blob: exclude blob object.
+ * tree: exclude tree object, blobs that the tree list, and recursive into sub-trees.
+ * commit: exclude commit object, and recursively exclude all the reachable trees
+ (ditto tree exclusion) and blobs it contains.
+ * tag: exclude tag object itself, and the dereference commit (ditto commit exclusion)
+ if the tag is annotated.
Configuration compatibility
-------------
--
2.31.1.456.gec51e24953
