From: Jason at zx2c4.com (Jason A. Donenfeld)
Subject: The road to v0.10.1 or v0.11
Date: Fri, 17 Jan 2014 17:38:29 +0100 [thread overview]
Message-ID: <CAHmME9rUbNW7Jkh2TDiXTJP+Z=+d7SgdgvWp3nPkcwL9ZdPdiQ@mail.gmail.com> (raw)
In-Reply-To: <20140117162851.GM7608@serenity.lan>
On Fri, Jan 17, 2014 at 5:28 PM, John Keeping <john at keeping.me.uk> wrote:
> I really can't see this being sensible without moving to libgit2. As
> long as we stick with libgit.a then we need to fork for each request so
> I'm not sure there's much benefit to supporting FastCGI without moving
> to something that lets us free resources when we're done processing a
> request.
The advantage would be not having to reparse the config and scan for
repos on every.single.solitary.request.
> I'd like to get "new graph implementation" into this list - it's come up
> on the list twice in the last 24 hours! That doesn't mean I'm claiming
> the task though ;-)
That's what I forgot!
+ new graph implementation
next prev parent reply other threads:[~2014-01-17 16:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-17 16:12 Jason
2014-01-17 16:28 ` john
2014-01-17 16:38 ` Jason [this message]
2014-01-17 16:53 ` john
2014-01-17 18:22 ` Jason
2014-01-17 19:29 ` mricon
2014-01-17 19:32 ` john
2014-01-17 22:37 ` Jason
2014-01-17 22:36 ` Jason
2014-01-17 17:09 ` Jason
2014-01-17 17:38 ` john
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='CAHmME9rUbNW7Jkh2TDiXTJP+Z=+d7SgdgvWp3nPkcwL9ZdPdiQ@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).