git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Sverre Rabbelier <srabbelier@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Allow cloning an empty repository
Date: Thu, 22 Jan 2009 17:24:27 -0800	[thread overview]
Message-ID: <7vwscm4xx0.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <1232669252-21881-1-git-send-email-srabbelier@gmail.com> (Sverre Rabbelier's message of "Fri, 23 Jan 2009 01:07:32 +0100")

Sverre Rabbelier <srabbelier@gmail.com> writes:

> diff --git a/builtin-clone.c b/builtin-clone.c
> index f7e5a7b..d5bba0e 100644
> --- a/builtin-clone.c
> +++ b/builtin-clone.c
> @@ -522,14 +522,23 @@ int cmd_clone(int argc, const char **argv, const char *prefix)
>  					     option_upload_pack);
>  
>  		refs = transport_get_remote_refs(transport);
> -		transport_fetch_refs(transport, refs);
> +		if(refs)
> +			transport_fetch_refs(transport, refs);

Thanks.

I think the basic idea is Ok, but is it a reliable check at this point to
see if (refs == NULL) to tell if the target repository is an empty one?

I am mostly worried about a failure case (connected but couldn't get the
refs, or perhaps connection failed to start).  If you get a NULL in such a
case you may end up saying "oh you cloned a void" when you should say
"nah, such a remote repository does not exist".

If transport_get_remote_refs() dies without returning NULL, that would be
sufficient, but I didn't check.

  reply	other threads:[~2009-01-23  1:26 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-23  0:07 [PATCH] Allow cloning an empty repository Sverre Rabbelier
2009-01-23  1:24 ` Junio C Hamano [this message]
2009-01-23  1:46   ` Sverre Rabbelier
2009-01-23  2:42     ` Johannes Schindelin
2009-01-23  2:47       ` Sverre Rabbelier
2009-01-23  3:20         ` Johannes Schindelin
2009-01-23 16:55           ` Miklos Vajna
2009-01-23 20:05             ` Johannes Schindelin
2009-01-23 22:32           ` Jeff King
2009-01-23 22:34             ` Sverre Rabbelier
2009-01-23 22:37               ` Jeff King
2009-01-23 22:39                 ` Sverre Rabbelier
2009-01-24  0:28                 ` Johannes Schindelin
2009-01-23 21:55       ` Mike Hommey
2009-01-24  0:26         ` http fixes, was " Johannes Schindelin
2009-01-24  9:39           ` Sverre Rabbelier
2009-01-23 23:05       ` Miklos Vajna
2009-01-24  0:33         ` Johannes Schindelin
2009-01-24  0:42           ` Sverre Rabbelier
2009-01-25  0:49             ` Miklos Vajna
2009-01-25  0:55               ` Sverre Rabbelier
2009-01-25  5:05                 ` Junio C Hamano
2009-01-25 18:33                   ` Sverre Rabbelier

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=7vwscm4xx0.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=srabbelier@gmail.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).