git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Imran M Yousuf" <imyousuf@gmail.com>
To: git@vger.kernel.org
Cc: gitster@pobox.com, "Imran M Yousuf" <imyousuf@smartitengineering.com>
Subject: Re: [PATCH] Documentation/git-submodule.txt: Add documentation for the recurse subcommand
Date: Mon, 5 May 2008 15:07:26 +0600	[thread overview]
Message-ID: <7bfdc29a0805050207s69f533e8ib78e6acdf7576ef6@mail.gmail.com> (raw)
In-Reply-To: <1209977051-25896-5-git-send-email-imyousuf@gmail.com>

Sorry for the inconvenience, but please ignore this patch as it was
not generated with -n and version number :(.

- best regards,

Imran


On Mon, May 5, 2008 at 2:44 PM,  <imyousuf@gmail.com> wrote:
> 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
>
>



-- 
Imran M Yousuf
Entrepreneur & Software Engineer
Smart IT Engineering
Dhaka, Bangladesh
Email: imran@smartitengineering.com
Mobile: +880-1711402557

  reply	other threads:[~2008-05-05  9:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-05  8:44 [PATCH] git-submodule.sh: Add Long Usage instead of simple usage imyousuf
2008-05-05  8:44 ` [PATCH] git-submodule.sh: Add recurse subcommand with basic options imyousuf
2008-05-05  8:44   ` [PATCH] git-submodule.sh: Add Custom argument input support to git submodule recurse subcommand imyousuf
2008-05-05  8:44     ` [PATCH] git-submodule.sh: Add pre command argument " imyousuf
2008-05-05  8:44       ` [PATCH] Documentation/git-submodule.txt: Add documentation for the " imyousuf
2008-05-05  9:07         ` Imran M Yousuf [this message]
2008-05-05  9:07       ` [PATCH] git-submodule.sh: Add pre command argument to git submodule " Imran M Yousuf
2008-05-05  9:07     ` [PATCH] git-submodule.sh: Add Custom argument input support " Imran M Yousuf
2008-05-05  9:08   ` [PATCH] git-submodule.sh: Add recurse subcommand with basic options Imran M Yousuf
2008-05-05  9:07 ` [PATCH] git-submodule.sh: Add Long Usage instead of simple usage Imran M Yousuf

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=7bfdc29a0805050207s69f533e8ib78e6acdf7576ef6@mail.gmail.com \
    --to=imyousuf@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=imyousuf@smartitengineering.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 NNTP newsgroup(s).