From: Jason at zx2c4.com (Jason A. Donenfeld)
Subject: Policy on global variables
Date: Thu, 16 Jan 2014 22:36:34 +0100 [thread overview]
Message-ID: <CAHmME9o1u3ev+cSnrwqRU-j9E6tPaF9-jHXKKd3e6MTZGAhtAw@mail.gmail.com> (raw)
In-Reply-To: <20140116213424.GI7608@serenity.lan>
On Thu, Jan 16, 2014 at 10:34 PM, John Keeping <john at keeping.me.uk> wrote:
>
> I'm not sure it makes much difference either way. Even if we use
> libgit2, providing we're not processing more than one request at once we
> can still use a global cgit_context.
Well, the idea of moving to libgit2, in the first place, would be to
benefit from its reentrancy, so that we could process multiple
requests at once (potentially).
next prev parent reply other threads:[~2014-01-16 21:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-16 0:06 Jason
2014-01-16 0:20 ` Jason
2014-01-16 0:59 ` normalperson
2014-01-16 1:00 ` Jason
2014-01-16 8:06 ` hjemli
2014-01-16 10:47 ` normalperson
2014-01-16 11:31 ` Jason
2014-01-16 13:08 ` john
2014-01-16 18:38 ` Jason
2014-01-16 21:21 ` john
2014-01-16 21:26 ` Jason
2014-01-16 21:34 ` john
2014-01-16 21:36 ` Jason [this message]
2014-01-16 22:20 ` john
2014-01-16 23:42 ` 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=CAHmME9o1u3ev+cSnrwqRU-j9E6tPaF9-jHXKKd3e6MTZGAhtAw@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).