From: "James via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: James <jdm12989@gmail.com>, James <jdm12989@gmail.com>
Subject: [PATCH] documentation: update git-submodule documentation
Date: Thu, 03 Nov 2022 10:26:33 +0000 [thread overview]
Message-ID: <pull.1401.git.1667471194097.gitgitgadget@gmail.com> (raw)
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
next reply other threads:[~2022-11-03 10:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-03 10:26 James via GitGitGadget [this message]
2022-11-03 12:14 ` [PATCH] documentation: update git-submodule documentation Ævar Arnfjörð Bjarmason
2022-11-04 11:25 ` James McCandlish
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=pull.1401.git.1667471194097.gitgitgadget@gmail.com \
--to=gitgitgadget@gmail.com \
--cc=git@vger.kernel.org \
--cc=jdm12989@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).