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

Re: [PATCH (take 2)] gitweb: Do not parse refs by hand, use git-peek-remote instead

From
Junio C Hamano <junkio@cox.net>
Date
Sep 15, 2006, 07:48 UTC
Message-ID
<7vvenpzi1h.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<eedjrj$tja$1@sea.gmane.org>
Jakub Narebski <jnareb@gmail.com> writes:
> But, if we change git_get_refs_list to do also work of git_get_references,
> we should also change git_get_references to not use info/refs file at all
> (it can, and usually for unknown reasons is stale) but always use
> git-peek-remote, for consistency.

Yes that would make sense. A repository served by gitweb does not necessarily has to serve objects over http transport, so it is nicer not to require info/refs to even exist or up to date.

Previous: Jakub NarebskiNext: Jakub Narebski
Message 6 of 9 in “gitweb: Do not parse refs by hand, use git-peek-remote instead”
  1. gitweb: Do not parse refs by hand, use git-peek-remote insteadJakub Narebski, Sep 14, 2006
  2. Junio C HamanoSep 14, 2006
  3. gitweb: Do not parse refs by hand, use git-peek-remote insteadJakub Narebski, Sep 15, 2006
  4. Junio C HamanoSep 15, 2006
  5. Jakub NarebskiSep 15, 2006
  6. Junio C HamanoSep 15, 2006
  7. Jakub NarebskiSep 15, 2006
  8. Junio C HamanoSep 15, 2006
  9. Jakub NarebskiSep 15, 2006

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.