From: list at eworm.de (Christian Hesse)
Subject: Idle column
Date: Fri, 19 Jul 2013 15:55:00 +0200 [thread overview]
Message-ID: <20130719155500.256f0118@leda> (raw)
In-Reply-To: <20130719114430.GD2337@serenity.lan>
John Keeping <john at keeping.me.uk> on Fri, 2013/07/19 12:44:
> 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
Ah, great! Looks like I misunderstood the agefile option.
Perhaps someone should add a note to the man page, probably I am not the only
one suffering this problem.
--
main(a){char*c=/* Schoene Gruesse */"B?IJj;MEH"
"CX:;",b;for(a/* Chris get my mail address: */=0;b=c[a++];)
putchar(b-1/(/* gcc -o sig sig.c && ./sig */b/42*2-3)*42);}
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 490 bytes
Desc: not available
URL: <http://lists.zx2c4.com/pipermail/cgit/attachments/20130719/5eaa13e8/attachment.asc>
next prev parent reply other threads:[~2013-07-19 13:55 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 [this message]
2013-07-22 7:15 ` list
2013-08-12 18:48 ` Jason
2013-07-22 13:13 ` mackyle
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=20130719155500.256f0118@leda \
--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).