git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] Git.pm: Add remote_refs() git-ls-remote frontend

From
Petr Baudis <pasky@suse.cz>
Date
Aug 30, 2007, 23:37 UTC
Message-ID
<20070830233714.GJ1219@pasky.or.cz>
In-Reply-To
<fb5vod$vvc$1@sea.gmane.org>
On Thu, Aug 30, 2007 at 10:39:41AM CEST, Jakub Narebski wrote:
Show 15 quoted lines
> [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...
But we want to typically list refs in a remote repository.
-- 
				Petr "Pasky" Baudis
Early to rise and early to bed makes a male healthy and wealthy and dead.
                -- James Thurber
Previous: Jakub NarebskiNext: Petr Baudis
Message 5 of 9 in “Git.pm: Add remote_refs() git-ls-remote frontend”
  1. Git.pm: Add remote_refs() git-ls-remote frontendPetr Baudis, Aug 25, 2007
  2. Junio C HamanoAug 26, 2007
  3. Petr BaudisAug 26, 2007
  4. Jakub NarebskiAug 30, 2007
  5. Petr BaudisAug 30, 2007
  6. Git.pm: Add remote_refs() git-ls-remote frontendPetr Baudis, Aug 30, 2007
  7. Junio C HamanoAug 31, 2007
  8. Petr BaudisAug 31, 2007
  9. Junio C HamanoAug 31, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.