[PATCH] documentation: update git-submodule documentation

From: James via GitGitGadget <gitgitgadget@gmail.com>
Date: Nov 3, 2022, 10:26 UTC
Message-ID: <pull.1401.git.1667471194097.gitgitgadget@gmail.com>

From: James <jdm12989@gmail.com>

Removes reference to custom code execution which is called out by gitmodules as not allowed.

Signed-off-by: James <jdm12989@gmail.com>
---
    Update git-submodule.txt
    
    Remove info about custom commands being allowed in the submodule update
    command to align with the gitmodules docs which states "For security
    reasons, the !command form is not accepted here."

Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-1401%2FEnochPrime%2Fsubmodule-docs-v1
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-1401/EnochPrime/submodule-docs-v1
Pull-Request: https://github.com/gitgitgadget/git/pull/1401

 Documentation/git-submodule.txt | 6 ------
 1 file changed, 6 deletions(-)

diff --git a/Documentation/git-submodule.txt b/Documentation/git-submodule.txt
index 4d3ab6b9f92..b40ac72f753 100644
--- a/Documentation/git-submodule.txt
+++ b/Documentation/git-submodule.txt
@@ -163,12 +163,6 @@ checked out in the submodule.
 The following 'update' procedures are only available via the
 `submodule.<name>.update` configuration variable:
 
-	custom command;; arbitrary shell command that takes a single
-	    argument (the sha1 of the commit recorded in the
-	    superproject) is executed. When `submodule.<name>.update`
-	    is set to '!command', the remainder after the exclamation mark
-	    is the custom command.
-
 	none;; the submodule is not updated.
 
 If the submodule is not yet initialized, and you just want to use the

base-commit: c03801e19cb8ab36e9c0d17ff3d5e0c3b0f24193

-- 
gitgitgadget