From: Junio C Hamano <junkio@cox.net>
Date: Fri, 03 Nov 2006 02:40:34 GMT
Subject: Re: [PATCH 2/2] gitweb: Use git-for-each-ref to generate list of heads and/or tags
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.

> 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.