From: Pavel Roskin <proski@gnu.org>
To: Sean <seanlkml@sympatico.ca>
Cc: git@vger.kernel.org, geoffrey.russell@gmail.com
Subject: Re: Problem upgrading to 1.4.0
Date: Mon, 12 Jun 2006 23:02:39 -0400 [thread overview]
Message-ID: <1150167759.4297.95.camel@dv> (raw)
In-Reply-To: <20060612224818.383b13ee.seanlkml@sympatico.ca>
Hi, Sean!
On Mon, 2006-06-12 at 22:48 -0400, Sean wrote:
> Hi Pavel,
>
> 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. If it's so good, shouldn't it be used unconditionally or at
least with minimal exceptions (some kinds of local clones)?
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2006-06-13 3:03 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 [this message]
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=1150167759.4297.95.camel@dv \
--to=proski@gnu.org \
--cc=geoffrey.russell@gmail.com \
--cc=git@vger.kernel.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).