git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael J Gruber <git@drmicha.warpmail.net>
To: dvilleneuve@kronos.com
Cc: git@vger.kernel.org
Subject: Re: exit status = 1 from git fetch -t
Date: Thu, 28 May 2009 09:56:33 +0200	[thread overview]
Message-ID: <4A1E43B1.20400@drmicha.warpmail.net> (raw)
In-Reply-To: <200905280357.n4S3v73G016535@hilo.ca.kronos.com>

Villeneuve venit, vidit, dixit 28.05.2009 05:57:
> Hi,
> 
> I'm getting an unexpected exit status of 1 from "git fetch
> -t" on one of our largest repositories (by large, I mean 47
> branches and 5442 tags, some of which might not be reachable
> from branch heads).
> 
> The docs are not clear about the interpretation of git
> fetch's exit status, so maybe I should not bother.
> 
> But assuming the exit status of 1 really indicates some
> trouble, here are more details.
> 
> Next tests done with git over ssh (server 1.6.1.3, client
> 1.6.3.1) on RHEL4.
> 
> In the "REPO1" repository (exit status printed just before $
> in prompt following command):
> 
> [REPO1] 0 $ git fetch -t -v -v
> Server supports multi_ack
> Server supports side-band-64k
> Server supports ofs-delta
> Marking 60e4d540748c5c3d368c888c4c248de0bdd684cc as complete
> Marking 60e4d540748c5c3d368c888c4c248de0bdd684cc as complete
> [REPO1] 1 $
> 
> while with another repository, "REPO2":
> 
> [REPO2] 0 $ git fetch -t -v -v
> From ssh://user@machine/path/to/GIT/dir1/dir2/REPO2
>  = [up to date]      v1.1 -> v1.1
>  = [up to date]      v1.2 -> v1.2
>  = [up to date]      v2.0 -> v2.0
> ... # lots of other similar lines
> [REPO2] 0 $
> 
> I've compiled git in debug to step in the code, and the
> source of the "error" exit status seems to come from
> builtin-fetch-pack.c:everything_local, where *refs being
> NULL leaves retval to 1 in the final loop.
> 
> I'm also puzzled that I don't get the "From ssh://..." in
> the trace from "REPO1" as for the "REPO2" repository above.
> I do get the "From ssh://..."  line if doing only "git fetch
> -v -v" without the "-t" option in "REPO1".

Looking at that loop, I reckon everything_local() returns 0 if there is
at least one object we "want" from the remote and 1 if there is none
(i.e. if "everything is local"). So that seems intentional. (The
structure of REPO1 and your fetch refspecs lines should explain why we
don't want anything.)

About the "From": If fetch displays no note (i.e. "foo   ref -> ref") it
displays no "From" either, which makes sense. We're not getting anything
from anywhere, we're not even listing up to date info, so we're not
displaying the reference point.

Michael

  reply	other threads:[~2009-05-28  7:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-28  3:57 exit status = 1 from git fetch -t Villeneuve
2009-05-28  7:56 ` Michael J Gruber [this message]
2009-05-28 14:56   ` Villeneuve, Daniel

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=4A1E43B1.20400@drmicha.warpmail.net \
    --to=git@drmicha.warpmail.net \
    --cc=dvilleneuve@kronos.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).