From: mackyle at gmail.com (Kyle J. McKay)
Subject: Idle column
Date: Mon, 22 Jul 2013 06:13:21 -0700 [thread overview]
Message-ID: <7311041D-23F6-4EFA-A510-49C074657177@gmail.com> (raw)
In-Reply-To: <20130719114430.GD2337@serenity.lan>
On Jul 19, 2013, at 04:44, John Keeping wrote:
> On Fri, Jul 19, 2013 at 01:29:52PM +0200, Christian Hesse wrote:
>> cgit is great and I enjoy it a lot. However it has one drawback
>> compared to
>> gitweb: The idle column in repository listing shows the age of a
>> (configurable) file from the repository. I think that is stupid
>> behavior as I
>> have a lot of "0 min." entries if I run "git gc" on my repositories
>> or the
>> date since last push or pull otherwise.
>>
>> In contrast to that gitweb shows the time since the last commit. I
>> would
>> prefer to have that in cgit as well. Any chance to get that? Or is
>> there any
>> good reason why the idle column is as is?
>
> This was discussed a couple of months ago [1]. You can use a hook and
> agefile to make CGit behave like GitWeb as described in that message.
>
> [1] http://article.gmane.org/gmane.comp.version-control.cgit/1059
Actually if you want it to behave like gitweb you'll need to use
something more like:
git for-each-ref --sort=-committerdate --format='%
(committerdate:iso8601)' \
--count=1 refs/heads > info/lastactivity
Since gitweb.perl actually uses:
open($fd, "-|", git_cmd(), 'for-each-ref',
'--format=%(committer)',
'--sort=-committerdate',
'--count=1',
'refs/heads') or return;
to get the timestamp which it uses to compute the age string.
prev parent reply other threads:[~2013-07-22 13:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-19 11:29 list
2013-07-19 11:44 ` john
2013-07-19 13:55 ` list
2013-07-22 7:15 ` list
2013-08-12 18:48 ` Jason
2013-07-22 13:13 ` mackyle [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7311041D-23F6-4EFA-A510-49C074657177@gmail.com \
--to=cgit@lists.zx2c4.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).