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

Re: [PATCH] gitweb: Move git_get_last_activity subroutine earlier

From
Junio C Hamano <junkio@cox.net>
Date
Oct 28, 2006, 19:24 UTC
Message-ID
<7v3b988cqn.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<ei0ags$l1l$1@sea.gmane.org>
Jakub Narebski <jnareb@gmail.com> writes:
Show 10 quoted lines
> Junio C Hamano wrote:
>
>> Why is this needed?
>  
> This is purely cosmetic, and originally was to be first patch in series
> converting git_summary, git_heads and git_tags to use of git-for-each-ref...
> but unfortunately git-for-each-ref lacks sorting on taggerdate OR
> committerdate (i.e. use taggerdate if applicable, committerdate otherwise).
>
> I'd rather not have git_get_last_activity between two parse_* subroutines...

Ok, will apply but the last line of your response _should_ have been in the proposed commit log message without being asked.

Previous: Jakub NarebskiNext: Junio C Hamano
Message 4 of 5 in “gitweb: Move git_get_last_activity subroutine earlier”
  1. gitweb: Move git_get_last_activity subroutine earlierJakub Narebski, Oct 28, 2006
  2. Junio C HamanoOct 28, 2006
  3. Jakub NarebskiOct 28, 2006
  4. Junio C HamanoOct 28, 2006
  5. Junio C HamanoOct 28, 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.