From: john at keeping.me.uk (John Keeping)
Subject: [PATCH] contrib/hooks: add sample post-receive hook using agefile
Date: Wed, 12 Aug 2015 16:04:46 +0100 [thread overview]
Message-ID: <20150812150446.GK30507@serenity.lan> (raw)
In-Reply-To: <CAHmME9oFHdzRLM-aLZPRdKzwCsq_YbyObCvsZZkmPJh9NNFFoA@mail.gmail.com>
On Wed, Aug 12, 2015 at 03:41:57PM +0200, Jason A. Donenfeld wrote:
> You might want to add this to
> http://git.zx2c4.com/cgit/about/faq
Something like this (which probably needs a bit of editing to make the
tone consistent with what's already there)?
-- >8 --
Subject: [PATCH] faq: add an entry about the agefile
Signed-off-by: John Keeping <john at keeping.me.uk>
---
faq | 13 +++++++++++++
1 file changed, 13 insertions(+)
diff --git a/faq b/faq
index 9c3ff01..e940510 100644
--- a/faq
+++ b/faq
@@ -26,3 +26,16 @@ the .git directory.
A less likely cause is that the repo is, infact, not a valid repo. Try
to run 'git show' in the offending repo to see if git also thinks your
repo has issues.
+
+
+### Why is the idle time for my repository wrong?
+
+By default CGit uses the modification time of the default branch's ref
+file as a quick method of determining when the repository was last
+changed. If you primarily work on other branches then this work will
+not be reflected in the idle time.
+
+You can use a post-receive hook to run a script that tells CGit the
+correct modification time by writing to ``info/web/last-modified``. An
+example is provided in the CGit repository at
+``contrib/hooks/post-receive.agefile``.
--
2.5.0.466.g9af26fa
prev parent reply other threads:[~2015-08-12 15:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-23 14:40 john
2014-12-23 15:15 ` mailings
2014-12-23 15:48 ` john
2014-12-23 16:12 ` mailings
2015-08-12 10:54 ` john
2015-08-12 12:05 ` Jason
2015-08-12 12:06 ` Jason
2015-08-12 13:41 ` Jason
2015-08-12 15:04 ` john [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=20150812150446.GK30507@serenity.lan \
--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).