git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@osdl.org>
To: Pavel Roskin <proski@gnu.org>
Cc: Sean <seanlkml@sympatico.ca>,
	git@vger.kernel.org, geoffrey.russell@gmail.com
Subject: Re: Problem upgrading to 1.4.0
Date: Mon, 12 Jun 2006 20:28:52 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0606122024400.5498@g5.osdl.org> (raw)
In-Reply-To: <1150167759.4297.95.camel@dv>



On Mon, 12 Jun 2006, Pavel Roskin wrote:
>
> > You can get a list of the remote branches whenever you want:
> > 
> > $ git ls-remote -h <remote>
> 
> I heard of that command.  But git-clone only uses it for local and rsync
> protocols.

The native format doesn't _need_ to use "git ls-remote", because the 
native format does it on its own.

In fact, "git ls-remote" actually uses the pack transfer protocol to 
figure out what the remote heads are (it just then doesn't _ask_ for 
anything), so in many ways you can see "git ls-remote" as being just a 
helper around the basic clone/pull protocol.

So "git clone" ends up doing the equivalent of a git ls-remote to populate 
the initial local heads and tags. It's just that for the native protocol, 
it all happens together in one burst.

		Linus

  reply	other threads:[~2006-06-13  3:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-11  0:07 Problem upgrading to 1.4.0 Geoff Russell
2006-06-11  2:12 ` Junio C Hamano
2006-06-13  2:33   ` Pavel Roskin
     [not found]     ` <20060612224818.383b13ee.seanlkml@sympatico.ca>
2006-06-13  2:48       ` Sean
2006-06-13  3:02       ` Pavel Roskin
2006-06-13  3:28         ` Linus Torvalds [this message]
2006-06-13  3:56           ` Pavel Roskin
2006-06-13  7:10             ` Geoff Russell

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=Pine.LNX.4.64.0606122024400.5498@g5.osdl.org \
    --to=torvalds@osdl.org \
    --cc=geoffrey.russell@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=proski@gnu.org \
    --cc=seanlkml@sympatico.ca \
    /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).