From: Ping Yin <pkufranky@gmail.com>
To: git@vger.kernel.org
Cc: gitster@pobox.com, Ping Yin <pkufranky@gmail.com>
Subject: [PATCH/RFC 7/7] git-submodule: "update --force" to enforce cloning non-submodule
Date: Thu, 10 Apr 2008 23:50:25 +0800 [thread overview]
Message-ID: <1207842625-9210-11-git-send-email-pkufranky@gmail.com> (raw)
In-Reply-To: <1207842625-9210-10-git-send-email-pkufranky@gmail.com>
If the update subcommand combines with --force, non-submodules
(i.e. modules existing in .gitmodules or $GIT_DIR/config but not added
to the super module) will be cloned and the master branch will be
checked out.
However, if a non-submodule has already been cloned before, the update
will be rejected since we don't know what the update means.
Signed-off-by: Ping Yin <pkufranky@gmail.com>
---
git-submodule.sh | 14 +++++++++++++-
1 files changed, 13 insertions(+), 1 deletions(-)
diff --git a/git-submodule.sh b/git-submodule.sh
index b4db676..153b61e 100755
--- a/git-submodule.sh
+++ b/git-submodule.sh
@@ -384,6 +384,9 @@ cmd_update()
-q|--quiet)
quiet=1
;;
+ -f | --force)
+ force="$1"
+ ;;
--)
shift
break
@@ -406,7 +409,8 @@ cmd_update()
test -z "$name" && exit_status=1 && continue
if test $sha1 = 0000000000000000000000000000000000000000
then
- say "Not a submodule: $name @ $path"
+ test -z "$force" &&
+ say "Not a submodule: $name @ $path" &&
continue
elif test -z "$url"
then
@@ -420,8 +424,15 @@ cmd_update()
if ! test -d "$path"/.git
then
! module_clone "$path" "$url" && exit_status=1 && continue
+ test "$sha1" = 0000000000000000000000000000000000000000 &&
+ (unset GIT_DIR; cd "$path" && git checkout -q master) &&
+ say "non-submodule cloned and master checked out: $name @ $path" &&
+ continue
subsha1=
else
+ test "$sha1" = 0000000000000000000000000000000000000000 &&
+ say "non-submodule already cloned: $name @ $path" &&
+ continue
subsha1=$(unset GIT_DIR; cd "$path" &&
git rev-parse --verify HEAD) ||
{
@@ -431,6 +442,7 @@ cmd_update()
}
fi
+
if test "$subsha1" != "$sha1"
then
(unset GIT_DIR; cd "$path" && git-fetch &&
--
1.5.5.23.g2a5f
next prev parent reply other threads:[~2008-04-10 15:52 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-10 15:50 [PATCH/RFC] submodule: fallback to .gitmodules and multiple level module definition Ping Yin
2008-04-10 15:50 ` [PATCH/RFC 1/7] git-submodule: Extract functions module_info and module_url Ping Yin
2008-04-10 15:50 ` [PATCH v2 1/3] git-submodule summary: --for-status option Ping Yin
2008-04-10 15:50 ` [PATCH v2 2/3] builtin-status: submodule summary support Ping Yin
2008-04-10 15:50 ` [PATCH/RFC 2/7] git-submodule: Extract absolute_url & move absolute url logic to module_clone Ping Yin
2008-04-10 15:50 ` [PATCH v2 3/3] buitin-status: Add tests for submodule summary Ping Yin
2008-04-10 15:50 ` [PATCH/RFC 3/7] git-submodule: Fall back on .gitmodules if info not found in $GIT_DIR/config Ping Yin
2008-04-10 15:50 ` [PATCH/RFC 4/7] git-submodule: Extract module_add from cmd_add Ping Yin
2008-04-10 15:50 ` [PATCH/RFC 5/7] git-submodule: multi-level module definition Ping Yin
2008-04-10 15:50 ` [PATCH/RFC 6/7] git-submodule: Don't die when command fails for one submodule Ping Yin
2008-04-10 15:50 ` Ping Yin [this message]
2008-04-11 23:24 ` [PATCH/RFC 3/7] git-submodule: Fall back on .gitmodules if info not found in $GIT_DIR/config Junio C Hamano
2008-04-11 23:24 ` Junio C Hamano
2008-04-12 4:26 ` Ping Yin
2008-04-11 21:56 ` [PATCH/RFC 2/7] git-submodule: Extract absolute_url & move absolute url logic to module_clone Junio C Hamano
2008-04-12 2:56 ` Ping Yin
2008-04-10 15:57 ` [PATCH v2 1/3] git-submodule summary: --for-status option Ping Yin
2008-04-11 22:30 ` [PATCH/RFC 1/7] git-submodule: Extract functions module_info and module_url Junio C Hamano
2008-04-12 3:05 ` Ping Yin
2008-04-12 4:50 ` 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=1207842625-9210-11-git-send-email-pkufranky@gmail.com \
--to=pkufranky@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).