From: cgit at cryptocrack.de (Lukas Fleischer)
Subject: Integration with Bugzilla?
Date: Sun, 26 Oct 2014 11:41:29 +0100 [thread overview]
Message-ID: <20141026104129.5022.81655@typhoon.lan> (raw)
In-Reply-To: <CAJFz9Pq6mo7g34NOVNnc4n+6KJ2o62JxoP7=YhVWT4wWjvVCVQ@mail.gmail.com>
On Fri, 24 Oct 2014 at 22:25:01, Joey Reid wrote:
> Yes, rewording the scan-path section of cgitrc.5 and adding an entry to
> the FAQ would be immensely helpful.
>
> The commit-links.sh and the trac script appear to spawn extra process. With
> servers like FreeDesktop's cgit under a heavy load, is there a way
> to minimize CPU usage?
> [...]
You can use Lua filters, check [1] for details.
[1] http://git.zx2c4.com/cgit/tree/cgitrc.5.txt#n582
prev parent reply other threads:[~2014-10-26 10:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-29 17:49 joeyisdamanya
2014-09-29 18:07 ` cgit
2014-09-29 18:09 ` mailings
2014-09-29 18:30 ` cgit
2014-09-29 18:33 ` mailings
2014-09-29 20:32 ` cgit
2014-10-22 1:22 ` joeyisdamanya
2014-10-22 6:29 ` hjemli
2014-10-24 20:25 ` joeyisdamanya
2014-10-26 10:41 ` cgit [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=20141026104129.5022.81655@typhoon.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).