List for cgit developers and users
 help / color / mirror / Atom feed
From: esajine at interactivebrokers.com (Eugene Sajine)
Subject: Cgit v0.9.2 problem with get_repo_modtime
Date: Thu, 15 Aug 2013 10:42:38 -0400	[thread overview]
Message-ID: <520CE8DE.8020100@interactivebrokers.com> (raw)
In-Reply-To: <20130814211404.GA20672@blizzard>

On 8/14/2013 5:14 PM, Lukas Fleischer wrote:
> On Wed, Aug 14, 2013 at 04:12:09PM -0400, Eugene Sajine wrote:
>> I have a minor problem with Cgit v 0.9.2 (upgraded from 0.8.3.3)
>>
>> Since i have updated the installation yesterday all repositories
>> that were shown as idle before for some time are now shown to be
>> idle for 4 days - all of them except for very recent ones. This
>> amount changes as the time passes (yesterday it was 3), but the
>> problem is that it is different from the actual time the repos were
>> touched. I.e. it is different from what i can see inside each repo.
> What does "touched" mean here? Did you really leave them untouched for
> more than four days? No `git push`, `git gc` or anything similar?

Well, we have more than 1300 repos, so some of them don't get any 
updates for quite a while, so it is possible to see no git push for 
weeks or months
I didn't know that "git gc" is counted as "touch" or "modification", so 
that makes now perfect sense - we do have weekly gc running. I don't 
think it was counted as such before (at v 0.8.3.3)

I will take a close look at the agefile

Thanks!

[1] http://lists.zx2c4.com/pipermail/cgit/2013-July/001443.html



  reply	other threads:[~2013-08-15 14:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.32.1376510774.1307.cgit@lists.zx2c4.com>
2013-08-14 20:12 ` esajine
2013-08-14 21:14   ` cgit
2013-08-15 14:42     ` esajine [this message]
2013-08-15 17:56       ` 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=520CE8DE.8020100@interactivebrokers.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).