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

Re: [PATCH 2/2] gitweb: Use git-for-each-ref to generate list of heads and/or tags

From
Junio C Hamano <junkio@cox.net>
Date
Nov 3, 2006, 02:40 UTC
Message-ID
<7vhcxhl0bh.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<200611022023.12246.jnareb@gmail.com>
Jakub Narebski <jnareb@gmail.com> writes:
> From 4d86b34d49dd1f18da465952be8306348fef5150 Mon Sep 17 00:00:00 2001
> From: Jakub Narebski <jnareb@gmail.com>
> Date: Thu, 2 Nov 2006 20:14:15 +0100
> Subject: [PATCH 2/2] gitweb: Use git-for-each-ref to generate list of heads and/or tags
The first line should not be in the body of the message.
Show 5 quoted lines
> CHANGES IN OUTPUT: Before, if ref in refs/tags was tag pointing to
> commit we used committer epoch as epoch for ref, and used tagger epoch
> as epoch only for tag pointing to object of other type. If ref in
> refs/tags was commit, we used committer epoch as epoch for ref (see
> parse_ref; we sorted in gitweb by 'epoch' field).

I think that behaviour was inconsistent and just silly. Using creatordate consistently is better so if the code generates what the commit log claims to, I think that is fine (I haven't looked at it deeply yet).

Thanks.  Will apply.
Previous: Jakub NarebskiNext: Jakub Narebski
Message 11 of 15 in “Documentation: Update information about <format> in git-for-each-ref”
  1. Documentation: Update information about <format> in git-for-each-refJakub Narebski, Oct 28, 2006
  2. Junio C HamanoOct 28, 2006
  3. Jakub NarebskiOct 28, 2006
  4. Andreas EricssonNov 1, 2006
  5. Junio C HamanoNov 1, 2006
  6. Andreas EricssonNov 1, 2006
  7. Junio C HamanoNov 1, 2006
  8. Johannes SchindelinNov 1, 2006
  9. 1/2 for-each-ref: "creator" and "creatordate" fieldsJakub Narebski, Nov 2, 2006
  10. 2/2 gitweb: Use git-for-each-ref to generate list of heads and/or tagsJakub Narebski, Nov 2, 2006
  11. Junio C HamanoNov 3, 2006
  12. Jakub NarebskiNov 3, 2006
  13. Junio C HamanoNov 3, 2006
  14. Jakub NarebskiNov 3, 2006
  15. 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.