git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Aneesh Kumar K.V" <aneesh.kumar@gmail.com>
To: "Aneesh Kumar K.V" <aneesh.kumar@gmail.com>, git@vger.kernel.org
Subject: [PATCH] FIX git pull failure with shallow clone changes
Date: Fri, 10 Nov 2006 11:57:10 +0530	[thread overview]
Message-ID: <45541BBE.4070303@gmail.com> (raw)
In-Reply-To: <45541503.4020604@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1 bytes --]



[-- Attachment #2: 0001-I-was-using-the-pu-branch-i-tried-to-update-the-git-repository-and-i.txt --]
[-- Type: text/plain, Size: 1470 bytes --]

I was using the pu branch i tried to update the git repository and i
got this error.

walk 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

Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@gmail.com>
---
 git-fetch.sh |    6 +++---
 1 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/git-fetch.sh b/git-fetch.sh
index 8b46e73..14ba4b2 100755
--- a/git-fetch.sh
+++ b/git-fetch.sh
@@ -314,9 +314,9 @@ fetch_main () {
 	      noepsv_opt="--disable-epsv"
 	  fi
 	  max_depth=5
-	  depth=0
+	  cur_depth=0
 	  head="ref: $remote_name"
-	  while (expr "z$head" : "zref:" && expr $depth \< $max_depth) >/dev/null
+	  while (expr "z$head" : "zref:" && expr $cur_depth \< $max_depth) >/dev/null
 	  do
 	    remote_name_quoted=$(@@PERL@@ -e '
 	      my $u = $ARGV[0];
@@ -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 \) )
+	    cur_depth=$( expr \( $cur_depth + 1 \) )
 	  done
 	  expr "z$head" : "z$_x40\$" >/dev/null ||
 	      die "Failed to fetch $remote_name from $remote"
-- 
1.4.4.rc1.g368c-dirty


  reply	other threads:[~2006-11-10  6:27 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
2006-11-10  6:27   ` Aneesh Kumar K.V [this message]
2006-11-13 12:26     ` [PATCH] FIX git pull failure with shallow clone changes 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=45541BBE.4070303@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 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).