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

gitweb some known issues

From
Junio C Hamano <junkio@cox.net>
Date
Nov 12, 2006, 06:28 UTC
Message-ID
<7virhlgov7.fsf@assigned-by-dhcp.cox.net>

Visit git.git gitweb page (http://repo.or.cz/w/git.git would work fine if git.kernel.org is too busy), and click on "GIT 1.4.4-rc1" to view the tag (not the commit).

The navigation bar has commit/commitdiff/tree with explicit h and hb object names that point at 'master', which feels wrong. When the tag that is displayed points at a commit, perhaps we would want to use that commit for commit and commitdiff? When the tag does not point at a commit (which is admittably very rare), probably not showing these links is the right thing to do (if tag points at tree it might make sense to give tree, though).

Also shortlog/log links do not say where to begin the log with, which means start digging from HEAD. When we display a commit or commitdiff, we seem to give a link to start log at that commit, so doing the same as above for shortlog/log may make them more consistent.

Message 1 of 1 in “gitweb some known issues”
  1. Junio C HamanoNov 12, 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.