List for cgit developers and users
 help / color / mirror / Atom feed
From: Jason at (Jason A. Donenfeld)
Subject: [PATCH] native inline gravatar
Date: Wed, 4 Jul 2018 03:05:33 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Wed, Jul 4, 2018 at 2:44 AM Andy Green <andy at> wrote:
> > looked at in depth. (See the list archives.) Our last conclusion from
> > examining it was that so much of libgit is not re-entrant, and so we'd
> > need to move to something like libgit2 for this to be feasible. Too
> > many globals, etc.
> Let me guess, not enough people around working on this project, for some
> reason, to move to libgit2.

No, actually. The reason is that we'd like to stay close to what
git.git is doing.

> If that's your feeling about the whole stack of clientside stuff, I
> understand you don't want to cooperate on it.

I think you misinterpreted me. I think the clientside work you're
doing is interesting and worth considering. I was speaking to somebody
earlier today who is actually working on a JSON API for cgit, so that
_all_ rendering can be done clientside.

What I'm specifically rejecting in my comment here is adding gravatar
support, some web service, in C directly to the core of cgit, when the
lua support has no demonstrable problems.

      reply	other threads:[~2018-07-04  1:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-01  3:20 andy
2018-07-03 23:49 ` Jason
2018-07-04  0:00   ` andy
2018-07-04  0:14     ` Jason
2018-07-04  0:28       ` andy
2018-07-04  0:34         ` Jason
2018-07-04  0:44           ` andy
2018-07-04  1:05             ` Jason [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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \

* 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).