Re: gitweb.cgi feature request: project list "last change" column to display last change of all heads.

[Jakub Narebski <jnareb@gmail.com>]

Pierre Marc Dumuid wrote:

>  I am working with the Cinelerra-CV group (cvs.cinelerra.org) and we are 
>  starting to use git to develop new patches.  Someone has offered to 
>  mirror our git branches to share amongst ourselves at 
>  http://www.pipapo.org/gitweb.
>  
>  The annoying thing is that in our mirrored personal repositories, we 
>  switch from head to head and push new features in different head, and 
>  then wait for the other developers to review.  At the moment, the 
>  getweb.cgi script only shows the "Last Change" for the current branch, 
>  and not all branches, (i.e. it's currently showing "13 days ago" for 
>  cinelerra-pmdumuid, whilst if you click the summary, you'll see I 
>  actually extended one of the branches only "24 hours ago".

This feature is planned (even if I forgot to mention it in the latest
"[RFC] gitweb wishlist and TODO list"[*1*] thread), but for performance
reasons it waits for git-for-each-ref to be in released version of git, as
it should be used for projects list to not be generated too slow.

But we could add it (although git is now in freezer before 1.4.3 release).
I was thinking about using 
  $feature{'lastchange'}{'default'} = HEAD | <branchname> | undef
where undef means search all branches for latest commit.

>  2nd feature request it the ability to browse to the next / previous 
>  commit when looking at a commitdiff...
 
First, merges can have more than one parent, so "previous" (or rather
"parent") can be ambiguous. Well, we could use first parent... But even
now it is fairly easy to go to the parent commitdiff: click on "commit"
link in the top navigation bar, or on the subject of commit; then click
on the "parent" link in the commit view; then click on "commitdiff" link
in the top navigation bar, or on the subject of commit.

Git philosophy and design precludes any kind of "next" link. Commit object
has only links to parents, never to children. If one really, really need
"next" link, one would need to save branch and where on branch we are
(in the git-name-rev way, e.g. b=HEAD~10) and pray somebody didn't update
the branch.

It should be quite easy to add commit+commitdiff view, though.

[*1*] http://marc.theaimsgroup.com/?t=115082282700003&r=1&w=2
      Msg-Id: <egdge3$t12$1@sea.gmane.org>
-- 
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git