* [PATCH v2] git-submodule: Don't die when command fails for one submodule
@ 2008-03-05 15:21 Ping Yin
2008-03-05 16:48 ` Johannes Schindelin
0 siblings, 1 reply; 3+ messages in thread
From: Ping Yin @ 2008-03-05 15:21 UTC (permalink / raw)
To: git; +Cc: gitster, Ping Yin
When handling multiple modules, init/update/status command will exit
when it fails for one submodule. This patch makes the command continue
bypassing the failure and keep right exit status.
Signed-off-by: Ping Yin <pkufranky@gmail.com>
---
git-submodule.sh | 110 ++++++++++++++++++++++++++++++++++++------------------
1 files changed, 74 insertions(+), 36 deletions(-)
diff --git a/git-submodule.sh b/git-submodule.sh
index 67d3224..3ad7214 100755
--- a/git-submodule.sh
+++ b/git-submodule.sh
@@ -100,15 +100,18 @@ module_clone()
# succeed but the rmdir will fail. We might want to fix this.
if test -d "$path"
then
- rmdir "$path" 2>/dev/null ||
- die "Directory '$path' exist, but is neither empty nor a git repository"
+ ! rmdir "$path" 2>/dev/null &&
+ say "Directory '$path' exist, but is neither empty nor a git repository" &&
+ return 1
fi
test -e "$path" &&
- die "A file already exist at path '$path'"
+ say "A file already exist at path '$path'" &&
+ return 1
- git-clone -n "$url" "$path" ||
- die "Clone of '$url' into submodule path '$path' failed"
+ ! git-clone -n "$url" "$path" &&
+ say "Clone of '$url' into submodule path '$path' failed" &&
+ return 1
}
#
@@ -156,7 +159,7 @@ cmd_add()
case "$repo" in
./*|../*)
# dereference source url relative to parent's url
- realrepo="$(resolve_relative_url $repo)" ;;
+ realrepo="$(resolve_relative_url $repo)" || return 1 ;;
*)
# Turn the source into an absolute path if
# it is local
@@ -175,21 +178,26 @@ cmd_add()
fi
test -e "$path" &&
- die "'$path' already exists"
+ say "'$path' already exists" &&
+ return 1
git ls-files --error-unmatch "$path" > /dev/null 2>&1 &&
- die "'$path' already exists in the index"
+ say "'$path' already exists in the index" &&
+ return 1
- module_clone "$path" "$realrepo" || exit
- (unset GIT_DIR; cd "$path" && git checkout -q ${branch:+-b "$branch" "origin/$branch"}) ||
- die "Unable to checkout submodule '$path'"
- git add "$path" ||
- die "Failed to add submodule '$path'"
+ module_clone "$path" "$realrepo" || return 1
+ ! (unset GIT_DIR; cd "$path" && git checkout -q ${branch:+-b "$branch" "origin/$branch"}) &&
+ say "Unable to checkout submodule '$path'" &&
+ return 1
+ ! git add "$path" &&
+ say "Failed to add submodule '$path'" &&
+ return 1
GIT_CONFIG=.gitmodules git config submodule."$path".path "$path" &&
GIT_CONFIG=.gitmodules git config submodule."$path".url "$repo" &&
- git add .gitmodules ||
- die "Failed to register submodule '$path'"
+ ! git add .gitmodules &&
+ say "Failed to register submodule '$path'" &&
+ return 1
}
#
@@ -221,29 +229,40 @@ cmd_init()
done
git ls-files --stage -- "$@" | grep -e '^160000 ' |
+ {
+ total=0
+ success=0
while read mode sha1 stage path
do
+ total=$(( $total + 1 ))
# Skip already registered paths
- name=$(module_name "$path") || exit
+ name=$(module_name "$path") || continue
url=$(git config submodule."$name".url)
- test -z "$url" || continue
+ test -n "$url" && success=$(( $success + 1 )) && continue
url=$(GIT_CONFIG=.gitmodules git config submodule."$name".url)
test -z "$url" &&
- die "No url found for submodule path '$path' in .gitmodules"
+ say "No url found for submodule path '$path' in .gitmodules" &&
+ continue
# Possibly a url relative to parent
case "$url" in
./*|../*)
- url="$(resolve_relative_url "$url")"
+ url="$(resolve_relative_url "$url")" || continue
;;
esac
- git config submodule."$name".url "$url" ||
- die "Failed to register url for submodule path '$path'"
-
- say "Submodule '$name' ($url) registered for path '$path'"
+ if git config submodule."$name".url "$url"
+ then
+ say "Submodule '$name' ($url) registered for path '$path'"
+ else
+ say "Failed to register url for submodule path '$path'"
+ continue
+ fi
+ success=$(( $success + 1 ))
done
+ test $success = $total
+ }
}
#
@@ -275,38 +294,53 @@ cmd_update()
done
git ls-files --stage -- "$@" | grep -e '^160000 ' |
+ {
+ total=0
+ success=0
while read mode sha1 stage path
do
- name=$(module_name "$path") || exit
+ total=$(( $total + 1 ))
+ name=$(module_name "$path") || continue
url=$(git config submodule."$name".url)
if test -z "$url"
then
# Only mention uninitialized submodules when its
# path have been specified
- test "$#" != "0" &&
- say "Submodule path '$path' not initialized"
+ if test "$#" != "0"
+ then
+ say "Submodule path '$path' not initialized"
+ else
+ success=$(( $success + 1 ))
+ fi
continue
fi
if ! test -d "$path"/.git
then
- module_clone "$path" "$url" || exit
+ module_clone "$path" "$url" || continue
subsha1=
else
- subsha1=$(unset GIT_DIR; cd "$path" &&
- git rev-parse --verify HEAD) ||
- die "Unable to find current revision in submodule path '$path'"
+ ! subsha1=$(unset GIT_DIR; cd "$path" &&
+ git rev-parse --verify HEAD 2>/dev/null) &&
+ say "Unable to find current revision in submodule path '$path'" &&
+ continue
fi
if test "$subsha1" != "$sha1"
then
- (unset GIT_DIR; cd "$path" && git-fetch &&
- git-checkout -q "$sha1") ||
- die "Unable to checkout '$sha1' in submodule path '$path'"
-
- say "Submodule path '$path': checked out '$sha1'"
+ if (unset GIT_DIR; cd "$path" && git-fetch &&
+ git-checkout -q "$sha1")
+ then
+ say "Submodule path '$path': checked out '$sha1'"
+ else
+ say "Unable to checkout '$sha1' in submodule path '$path'"
+ continue
+ fi
fi
+ success=$(( $success + 1 ))
done
+ test $success = $total
+ }
}
set_name_rev () {
@@ -358,9 +392,11 @@ cmd_status()
done
git ls-files --stage -- "$@" | grep -e '^160000 ' |
+ {
+ exit_status=0
while read mode sha1 stage path
do
- name=$(module_name "$path") || exit
+ ! name=$(module_name "$path") && exit_status=1 && continue
url=$(git config submodule."$name".url)
if test -z "$url" || ! test -d "$path"/.git
then
@@ -380,6 +416,8 @@ cmd_status()
say "+$sha1 $path$revname"
fi
done
+ exit $exit_status
+ }
}
# This loop parses the command line arguments to find the
--
1.5.4.3.347.g5314c
^ permalink raw reply related [flat|nested] 3+ messages in thread
* Re: [PATCH v2] git-submodule: Don't die when command fails for one submodule
2008-03-05 15:21 [PATCH v2] git-submodule: Don't die when command fails for one submodule Ping Yin
@ 2008-03-05 16:48 ` Johannes Schindelin
2008-03-05 17:20 ` Ping Yin
0 siblings, 1 reply; 3+ messages in thread
From: Johannes Schindelin @ 2008-03-05 16:48 UTC (permalink / raw)
To: Ping Yin; +Cc: git, gitster
Hi,
On Wed, 5 Mar 2008, Ping Yin wrote:
> @@ -221,29 +229,40 @@ cmd_init()
> done
>
> git ls-files --stage -- "$@" | grep -e '^160000 ' |
> + {
> + total=0
> + success=0
> while read mode sha1 stage path
> do
> + total=$(( $total + 1 ))
> # Skip already registered paths
> - name=$(module_name "$path") || exit
> + name=$(module_name "$path") || continue
What about this case? Was the comment misleading?
> url=$(git config submodule."$name".url)
> - test -z "$url" || continue
> + test -n "$url" && success=$(( $success + 1 )) && continue
Why counting? Why not just 'status=0 && continue'?
>
> - git config submodule."$name".url "$url" ||
> - die "Failed to register url for submodule path '$path'"
> -
> - say "Submodule '$name' ($url) registered for path '$path'"
> + if git config submodule."$name".url "$url"
> + then
> + say "Submodule '$name' ($url) registered for path '$path'"
> + else
> + say "Failed to register url for submodule path '$path'"
> + continue
> + fi
> + success=$(( $success + 1 ))
> done
> + test $success = $total
> + }
> }
>
> #
Note: I have not even begun to audit if one of your returns should not
have been a "status=0 && continue" instead.
> @@ -358,9 +392,11 @@ cmd_status()
> done
>
> git ls-files --stage -- "$@" | grep -e '^160000 ' |
> + {
> + exit_status=0
> while read mode sha1 stage path
> do
> - name=$(module_name "$path") || exit
> + ! name=$(module_name "$path") && exit_status=1 && continue
> url=$(git config submodule."$name".url)
> if test -z "$url" || ! test -d "$path"/.git
> then
> @@ -380,6 +416,8 @@ cmd_status()
> say "+$sha1 $path$revname"
> fi
> done
> + exit $exit_status
> + }
> }
But here you use the simpler paradigm of setting exit_status? Why that
complicated and ugly "total" and "success" counting before?
Ciao,
Dscho
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [PATCH v2] git-submodule: Don't die when command fails for one submodule
2008-03-05 16:48 ` Johannes Schindelin
@ 2008-03-05 17:20 ` Ping Yin
0 siblings, 0 replies; 3+ messages in thread
From: Ping Yin @ 2008-03-05 17:20 UTC (permalink / raw)
To: Johannes Schindelin; +Cc: git, gitster
On Thu, Mar 6, 2008 at 12:48 AM, Johannes Schindelin
<Johannes.Schindelin@gmx.de> wrote:
> Hi,
>
>
> On Wed, 5 Mar 2008, Ping Yin wrote:
>
> > @@ -221,29 +229,40 @@ cmd_init()
> > done
> >
> > git ls-files --stage -- "$@" | grep -e '^160000 ' |
> > + {
> > + total=0
> > + success=0
> > while read mode sha1 stage path
> > do
> > + total=$(( $total + 1 ))
> > # Skip already registered paths
> > - name=$(module_name "$path") || exit
> > + name=$(module_name "$path") || continue
>
> What about this case? Was the comment misleading?
>
>
> > url=$(git config submodule."$name".url)
> > - test -z "$url" || continue
> > + test -n "$url" && success=$(( $success + 1 )) && continue
>
> Why counting? Why not just 'status=0 && continue'?
>
>
> >
> > - git config submodule."$name".url "$url" ||
> > - die "Failed to register url for submodule path '$path'"
> > -
> > - say "Submodule '$name' ($url) registered for path '$path'"
> > + if git config submodule."$name".url "$url"
> > + then
> > + say "Submodule '$name' ($url) registered for path '$path'"
> > + else
> > + say "Failed to register url for submodule path '$path'"
> > + continue
> > + fi
> > + success=$(( $success + 1 ))
> > done
> > + test $success = $total
> > + }
> > }
> >
> > #
>
> Note: I have not even begun to audit if one of your returns should not
> have been a "status=0 && continue" instead.
>
>
> > @@ -358,9 +392,11 @@ cmd_status()
> > done
> >
> > git ls-files --stage -- "$@" | grep -e '^160000 ' |
> > + {
> > + exit_status=0
> > while read mode sha1 stage path
> > do
> > - name=$(module_name "$path") || exit
> > + ! name=$(module_name "$path") && exit_status=1 && continue
> > url=$(git config submodule."$name".url)
> > if test -z "$url" || ! test -d "$path"/.git
> > then
> > @@ -380,6 +416,8 @@ cmd_status()
> > say "+$sha1 $path$revname"
> > fi
> > done
> > + exit $exit_status
> > + }
> > }
>
> But here you use the simpler paradigm of setting exit_status? Why that
> complicated and ugly "total" and "success" counting before?
>
> Ciao,
> Dscho
>
>
'total' and 'success' is a trick which i think is simpler than
exit_status=1/exit_status=0 in cmd_update and cmd_init.
In the while loop of these two functions, there are many tests which
will continue the loop after a failure. By using exit_stauts, i have
to replace 'cmd || continue' as '! cmd && exit_status=1 && continue".
I don't want so many exit_status in the while loop. So i use 'total'
and 'sucess' which count the total number of loops and the number of
successful loops separately to simplify this. The trick is as follows:
'total' will plus 1 when at the beginning of a loop and success will
plus 1 at the end of loop. If a loop succeeds and continues in the
middle of a loop, success also plus 1. Failed loops never reach the
loop end so success will not plus 1.
After leaving all loops, $sucess=$total means all loops succeed and
exit status should be 0, or exit status should be 1.
In cmd_status, the 'cmd || continue' only exists in one place, so i
use exit_status instead of 'success' and 'total'.
--
Ping Yin
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2008-03-05 17:21 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2008-03-05 15:21 [PATCH v2] git-submodule: Don't die when command fails for one submodule Ping Yin
2008-03-05 16:48 ` Johannes Schindelin
2008-03-05 17:20 ` Ping Yin
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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).