From: "Aneesh Kumar K.V" <aneesh.kumar@gmail.com>
To: "Aneesh Kumar K.V" <aneesh.kumar@gmail.com>, git@vger.kernel.org
Subject: Re: shallow clone failed git pull
Date: Fri, 10 Nov 2006 11:28:27 +0530 [thread overview]
Message-ID: <45541503.4020604@gmail.com> (raw)
In-Reply-To: <4552A865.5000201@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 682 bytes --]
Aneesh Kumar K.V wrote:
> I was using the pu branch i tried to update the git repository and i got
> this error.
>
> alk 9e950efa20dc8037c27509666cba6999da9368e8
> walk 3b6a792f6ace33584897d1af08630c9acc0ce221
> * refs/heads/origin: fast forward to branch 'master' of
> http://repo.or.cz/r/linux-2.6
> old..new: 3d42488..088406b
> Auto-following refs/tags/v2.6.19-rc5
> shallow clone with http not supported
>
>
> This repository was not cloned with -depth. I only updated the git tools
> using the pu branch
>
The attached patch gets it working. I am not sure whether the fix is the right one. I
am a little bit confused regarding the $depth being incremented.
-aneesh
[-- Attachment #2: git-fetch.sh.diff --]
[-- Type: text/x-patch, Size: 1402 bytes --]
diff --git a/git-fetch.sh b/git-fetch.sh
index 8b46e73..6459994 100755
--- a/git-fetch.sh
+++ b/git-fetch.sh
@@ -21,7 +21,7 @@ update_head_ok=
exec=
upload_pack=
keep=
-depth=
+depth=0
while case "$#" in 0) break ;; esac
do
case "$1" in
@@ -304,7 +304,7 @@ fetch_main () {
# There are transports that can fetch only one head at a time...
case "$remote" in
http://* | https://* | ftp://*)
- test -n "$depth" && die "shallow clone with http not supported"
+ [ x"$depth" != x0 ] && die "shallow clone with http not supported"
proto=`expr "$remote" : '\([^:]*\):'`
if [ -n "$GIT_SSL_NO_VERIFY" ]; then
curl_extra_args="-k"
@@ -325,7 +325,7 @@ fetch_main () {
print "$u";
' "$head")
head=$(curl -nsfL $curl_extra_args $noepsv_opt "$remote/$remote_name_quoted")
- depth=$( expr \( $depth + 1 \) )
+ # depth=$( expr \( $depth + 1 \) )
done
expr "z$head" : "z$_x40\$" >/dev/null ||
die "Failed to fetch $remote_name from $remote"
@@ -333,7 +333,7 @@ fetch_main () {
git-http-fetch -v -a "$head" "$remote/" || exit
;;
rsync://*)
- test -n "$depth" && die "shallow clone with rsync not supported"
+ [ x"$depth" != x0 ] && die "shallow clone with http not supported"
TMP_HEAD="$GIT_DIR/TMP_HEAD"
rsync -L -q "$remote/$remote_name" "$TMP_HEAD" || exit 1
head=$(git-rev-parse --verify TMP_HEAD)
next prev parent reply other threads:[~2006-11-10 5:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-09 4:02 shallow clone failed git pull Aneesh Kumar K.V
2006-11-10 5:58 ` Aneesh Kumar K.V [this message]
2006-11-10 6:27 ` [PATCH] FIX git pull failure with shallow clone changes Aneesh Kumar K.V
2006-11-13 12:26 ` Johannes Schindelin
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=45541503.4020604@gmail.com \
--to=aneesh.kumar@gmail.com \
--cc=git@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.