git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Fredrik Gustafsson <iveqy@iveqy.com>
To: git@vger.kernel.org
Cc: jens.lehmann@web.de, hvoigt@hvoigt.net, gitster@pobox.com
Subject: [RFC PATCH 0/2] submodule update continue
Date: Sun, 15 May 2011 14:42:19 +0200	[thread overview]
Message-ID: <cover.1305462132.git.iveqy@iveqy.com> (raw)

When running submodule update git dies after the first error. This is
inconvenient if a submodule is unavailable. Therefore this patch series
makes git continue with the next submodule if a submodule is
unavailable.

This does only apply to checkout errors, rebase and merge errors will
result with a direct exit with code 2.

A checkout error makes git continue to the next submodule and when done
with all submodules exit with code 1.

Still missing are three tests (recursive checkout, merge and recurive rebase).

This is the second iteration of this patch series. The first can be
found on:
http://thread.gmane.org/gmane.comp.version-control.git/171895

Fredrik Gustafsson (2):
  sh-setup: Make die take the error code as param.
  submodule update: continue when a checkout fails

 git-sh-setup.sh             |    6 +++++-
 git-submodule.sh            |   42 ++++++++++++++++++++++++++++++++++++------
 t/t7406-submodule-update.sh |   29 +++++++++++++++++++++++++++++
 3 files changed, 70 insertions(+), 7 deletions(-)

-- 
1.7.5.1.219.ge2152.dirty

             reply	other threads:[~2011-05-15 12:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-15 12:42 Fredrik Gustafsson [this message]
2011-05-15 12:42 ` [RFC PATCH 1/2] sh-setup: Make die take the error code as param Fredrik Gustafsson
2011-05-15 20:46   ` Junio C Hamano
2011-05-15 12:42 ` [RFC PATCH 2/2] submodule update: continue when a checkout fails Fredrik Gustafsson
2011-05-15 21:26   ` Junio C Hamano

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=cover.1305462132.git.iveqy@iveqy.com \
    --to=iveqy@iveqy.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=hvoigt@hvoigt.net \
    --cc=jens.lehmann@web.de \
    /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).