From: hjemli at gmail.com (Lars Hjemli)
Subject: Branch Age Sorting and Idle Most Recent Sorting [Was: Re: Today is a big day for us]
Date: Wed, 6 Mar 2013 07:24:20 +0100 [thread overview]
Message-ID: <CAFXTnz5_rMu8guiUNrZ=cX0FMM9Ko6Gp16VcVwnKzriugHg3jg@mail.gmail.com> (raw)
In-Reply-To: <CAHmME9o0FDJOC+ukx1kmz-MSOgEVZu2LTFXSbyECFTwq_p06JQ@mail.gmail.com>
> On Tue, Mar 5, 2013 at 2:30 PM, Konstantin Ryabitsev <mricon at kernel.org> wrote:
>>> It seems to me that the "Idle" column in global view reflects the last
>>> change on master branch of a given repository, but most of the development
>>> is happening on other branches, so this doesn't give any good overview
>>> about how alive the repository is. gitweb was always showing the time
>>> elapsed from latest modification on any of the branches in the repository.
To make cgits idle-time appear similar to gitwebs, one can use the
'agefile' (http://git.zx2c4.com/cgit/tree/cgitrc.5.txt#n36) combined
with a git hook in each repository.
As an example, here is the post-receive hook installed in the cgit
repo on hjemli.net:
#!/bin/sh
cd /pub/git/cgit
git for-each-ref --sort=-authordate --format='%(authordate:iso8601)'
--count=1 >info/touched
By doing it this way, the loading of the index page is a much cheaper
operation (which is especially important on a heavily used site like
kernel.org).
--
larsh
next prev parent reply other threads:[~2013-03-06 6:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-06 0:29 Jason
2013-03-06 6:24 ` hjemli [this message]
[not found] ` <5136A26A.1060303@kernel.org>
2013-03-20 20:00 ` Jason
2013-03-20 20:13 ` john
2013-04-08 15:10 ` Jason
2013-04-08 17:44 ` john
2013-04-08 15:09 ` Jason
[not found] ` <20130408151701.GA2674@gmail.com>
2013-04-10 12:53 ` Jason
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='CAFXTnz5_rMu8guiUNrZ=cX0FMM9Ko6Gp16VcVwnKzriugHg3jg@mail.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).