git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johan Herland <johan@herland.net>
To: git@vger.kernel.org
Cc: Johan Herland <johan@herland.net>,
	gitster@pobox.com, mlevedahl@gmail.com, hjemli@gmail.com
Subject: [RFC/PATCH 0/6] Git submodule: 'foreach' enhancements and nested submodule handling
Date: Wed, 19 Aug 2009 03:45:18 +0200	[thread overview]
Message-ID: <1250646324-961-1-git-send-email-johan@herland.net> (raw)

Hi,

This patch series attempts to expand 'git submodule' command in two
regards:

1. Clean up, selftest, and enhance the 'git submodule foreach' command.
2. Provide better handling for nested submodules where the user want to
   operate on _all_ submodules simultenously.

The first 3 patches in the series are fairly trivial and straightforward.
The last 3 patches are slightly more RFC in nature, although their
implementation is still fairly straighforward.

Patch 3/6 is a resend of a patch that I sent stand-alone on 2009-08-16.


Have fun! :)

...Johan


Johan Herland (6):
  git submodule: Cleanup usage string and add option parsing to cmd_foreach()
  Add selftest for 'git submodule foreach'
  git submodule foreach: Provide access to submodule name, as '$name'
  git submodule foreach: Add --recursive to recurse into nested submodules
  git submodule update: Introduce --recursive to update nested submodules
  git submodule status: Add --recursive to recurse into nested submodules

 Documentation/git-submodule.txt |   23 ++++-
 git-submodule.sh                |   79 ++++++++++++--
 t/t7407-submodule-foreach.sh    |  223 +++++++++++++++++++++++++++++++++++++++
 3 files changed, 313 insertions(+), 12 deletions(-)
 create mode 100755 t/t7407-submodule-foreach.sh

             reply	other threads:[~2009-08-19  1:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-19  1:45 Johan Herland [this message]
2009-08-19  1:45 ` [RFC/PATCH 1/6] git submodule: Cleanup usage string and add option parsing to cmd_foreach() Johan Herland
2009-08-19  1:45 ` [RFC/PATCH 2/6] Add selftest for 'git submodule foreach' Johan Herland
2009-08-19  1:45 ` [RFC/PATCH 3/6] git submodule foreach: Provide access to submodule name, as '$name' Johan Herland
2009-08-19  1:45 ` [RFC/PATCH 4/6] git submodule foreach: Add --recursive to recurse into nested submodules Johan Herland
2009-08-19  1:45 ` [RFC/PATCH 5/6] git submodule update: Introduce --recursive to update " Johan Herland
2009-08-19  1:45 ` [RFC/PATCH 6/6] git submodule status: Add --recursive to recurse into " Johan Herland
2009-08-19 23:07 ` [RFC/PATCH 7/6] git clone: Add --recursive to automatically checkout (nested) submodules Johan Herland

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=1250646324-961-1-git-send-email-johan@herland.net \
    --to=johan@herland.net \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=hjemli@gmail.com \
    --cc=mlevedahl@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 NNTP newsgroup(s).