From: Jakub Narebski <jnareb@gmail•com>
To: git@vger•kernel.org
Subject: Re: [PATCH] Git.pm: Add remote_refs() git-ls-remote frontend
Date: Thu, 30 Aug 2007 10:39:41 +0200 [thread overview]
Message-ID: <fb5vod$vvc$1@sea.gmane.org> (raw)
In-Reply-To: 20070825221143.6514.22516.stgit@rover
[Cc: Petr Baudis <pasky@suse•cz>, git@vger•kernel.org]
Petr Baudis wrote:
> Should support all the important features, I guess. Too bad that
> git-ls-remote --heads .
>
> is subtly different from
>
> git-ls-remote . refs/heads/
>
> so we have to provide the interface for specifying both.
Why do not use git-for-each-ref or git-show-refs? If I remember correctly
they _were_ faster than git-ls-remote or git-peek-remote...
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
next prev parent reply other threads:[~2007-08-30 8:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-25 22:11 [PATCH] Git.pm: Add remote_refs() git-ls-remote frontend Petr Baudis
2007-08-26 4:26 ` Junio C Hamano
2007-08-26 9:58 ` Petr Baudis
2007-08-30 8:39 ` Jakub Narebski [this message]
2007-08-30 23:37 ` Petr Baudis
2007-08-30 23:37 ` Petr Baudis
2007-08-31 0:26 ` Junio C Hamano
2007-08-31 1:37 ` Petr Baudis
2007-08-31 2:13 ` Junio C Hamano
-- strict thread matches above, loose matches on Subject: below --
2008-07-08 17:48 Petr Baudis
2007-05-17 2:37 Petr Baudis
2007-05-17 5:58 ` Junio C Hamano
2007-05-17 11:30 ` Petr Baudis
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='fb5vod$vvc$1@sea.gmane.org' \
--to=jnareb@gmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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