git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH v2 5/5] Documentation/git-submodule.txt: Add documentation for the recurse subcommand

From
imyousuf@gmail.com <imyousuf@gmail.com>
Date
May 5, 2008, 09:09 UTC
Message-ID
<1209978582-5785-5-git-send-email-imyousuf@gmail.com>
In-Reply-To
<1209978582-5785-4-git-send-email-imyousuf@gmail.com>
From: Imran M Yousuf <imyousuf@smartitengineering.com>

Documentation with brief description is added for the recurse sucommand along with its arguments and their nature.

Signed-off-by: Imran M Yousuf <imyousuf@smartitengineering.com>
---
 Documentation/git-submodule.txt |   35 +++++++++++++++++++++++++++++++++++
 1 files changed, 35 insertions(+), 0 deletions(-)
diff --git a/Documentation/git-submodule.txt b/Documentation/git-submodule.txt
index 6ffd896..9a95522 100644
--- a/Documentation/git-submodule.txt
+++ b/Documentation/git-submodule.txt
@@ -13,6 +13,10 @@ SYNOPSIS
 'git-submodule' [--quiet] status [--cached] [--] [<path>...]
 'git-submodule' [--quiet] [init|update] [--] [<path>...]
 'git-submodule' [--quiet] summary [--summary-limit <n>] [commit] [--] [<path>...]
+'git-submodule' recurse [-q|--quiet] [-e|--exit-after-error]
+		[-d|--depth <recursion depth>] [-b|--breadth-first]
+		[-a|--customized-argument] [-p|--pre-command]
+		<git command> [<arg> ...]"
 
 
 COMMANDS
@@ -54,6 +58,10 @@ summary::
 	in the submodule between the given super project commit and the
 	index or working tree (switched by --cached) are shown.
 
+recurse::
+	Recurse, IOW propagate, command to its submodules if they are
+	initialized.
+
 OPTIONS
 -------
 -q, --quiet::
@@ -78,6 +86,33 @@ OPTIONS
 	Path to submodule(s). When specified this will restrict the command
 	to only operate on the submodules found at the specified paths.
 
+-e, --exit-after-error::
+	This option is only valid for the recurse command. If its provided then
+	then command will not be recursed into any other module once a command
+	has failed
+-d, --depth <recursion depth>::
+	This option is only valid for the recurse command. If its provided then
+	then the command will be recursed upto <recursion depth> only.
+-b, --breadth-first::
+	This option is only valid for the recurse command. If its provided then
+	the command will execute in the current node before traversing to its
+	child, else it will first traverse the children before executing in the
+	current node.
+-a, --customized-argument::
+	This option is only valid for the recurse command. If its provided then
+	user will be prompted for an argument for the <git command> specified.
+	Its particularly useful when one wants to supply different arguments
+	for the same <git command> for different submodules; for example,
+	checking out a branch, one might want branch to differ from submodule
+	to submodule
+-p, --pre-command::
+	This option is only valid for the recurse command. If its provided then
+	user will be prompted for a shell command, e.g. 'ls -al', 'pwd' etc.
+<git command> [<arg>...]::
+	Any git command and their argument. For example, to get the status use
+	'status' as <git command> and '-s' or '-o' or any other 'git status'
+	arguments as <arg>
+
 FILES
 -----
 When initializing submodules, a .gitmodules file in the top-level directory
-- 
1.5.4.2
Previous: imyousuf@gmail.comNext: Junio C Hamano
Message 5 of 13 in “git-submodule.sh: Add Long Usage instead of simple usage”
  1. 1/5 git-submodule.sh: Add Long Usage instead of simple usageimyousuf@gmail.com, May 5, 2008
  2. 2/5 git-submodule.sh: Add recurse subcommand with basic optionsimyousuf@gmail.com, May 5, 2008
  3. 3/5 git-submodule.sh: Add Custom argument input support to git submodule recurse subcommandimyousuf@gmail.com, May 5, 2008
  4. 4/5 git-submodule.sh: Add pre command argument to git submodule recurse subcommandimyousuf@gmail.com, May 5, 2008
  5. 5/5 Documentation/git-submodule.txt: Add documentation for the recurse subcommandimyousuf@gmail.com, May 5, 2008
  6. Junio C HamanoMay 12, 2008
  7. Johan HerlandMay 18, 2008
  8. Sverre RabbelierMay 18, 2008
  9. Johannes SchindelinMay 18, 2008
  10. Sverre RabbelierMay 18, 2008
  11. Imran M YousufMay 19, 2008
  12. Junio C HamanoMay 12, 2008
  13. Imran M YousufMay 13, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.