git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sean <seanlkml@sympatico.ca>
To: Pavel Roskin <proski@gnu.org>
Cc: git@vger.kernel.org, geoffrey.russell@gmail.com
Subject: Re: Problem upgrading to 1.4.0
Date: Mon, 12 Jun 2006 22:48:18 -0400	[thread overview]
Message-ID: <BAYC1-PASMTP057F6CD43B793C898A6952AE8C0@CEZ.ICE> (raw)
Message-ID: <20060612224818.383b13ee.seanlkml@sympatico.ca> (raw)
In-Reply-To: <1150165982.4297.88.camel@dv>

On Mon, 12 Jun 2006 22:33:02 -0400
Pavel Roskin <proski@gnu.org> wrote:

> And while at that, it would be great to download and keep the list of
> the remote branches, perhaps when requested with a special switch.  It
> doesn't mean that all of the branches should be fetched, but it would be
> nice to have a list of the available remove branches somewhere.
> 
> As it stands now, this functionality is implemented in git-clone, which
> it probably not the best place.  Users should not be forced to clone the
> directory again to find out which branches are available.

Hi Pavel,

You can get a list of the remote branches whenever you want:

$ git ls-remote -h <remote>

So, to see available branches in the repo from which you initially
cloned:

$ git ls-remote -h origin

Or to see which branches are available in the official cogito repo,
without ever cloning it:

$ git ls-remote -h git://git.kernel.org/pub/scm/cogito/cogito.git

HTH,
Sean

  reply	other threads:[~2006-06-13  2:49 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 [this message]
2006-06-13  3:02       ` Pavel Roskin
2006-06-13  3:28         ` Linus Torvalds
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=BAYC1-PASMTP057F6CD43B793C898A6952AE8C0@CEZ.ICE \
    --to=seanlkml@sympatico.ca \
    --cc=geoffrey.russell@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=proski@gnu.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).