List for cgit developers and users
 help / color / mirror / Atom feed
From: Jason at zx2c4.com (Jason A. Donenfeld)
Subject: Policy on global variables
Date: Thu, 16 Jan 2014 19:38:02 +0100	[thread overview]
Message-ID: <CAHmME9oU=4JZA9AX-f5BfKd_MeMH-k5_M+0fegBkhs4eiTMWhQ@mail.gmail.com> (raw)
In-Reply-To: <20140116130844.GF7608@serenity.lan>

On Thu, Jan 16, 2014 at 2:08 PM, John Keeping <john at keeping.me.uk> wrote:
>
> I had a look at porting to libgit2 about a year ago and it mostly isn't
> too bad.  IIRC the only problematic area is the graph output which we
> currently get from libgit.a but would have to do ourselves if we switch
> to libgit2.

Are there any downsides of doing this? I know we've put a lot of work
into cozying up with internal git utility functions and their build
system. Would we have to reimplement a lot of this? Would it be worth
it? Are there general benefits of using libgit2 over what we have now?
Are there general downsides?

More importantly, is this something you would be willing to do, if we
decided it was the best direction?


  reply	other threads:[~2014-01-16 18:38 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 [this message]
2014-01-16 21:21               ` john
2014-01-16 21:26                 ` Jason
2014-01-16 21:34                   ` john
2014-01-16 21:36                     ` Jason
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='CAHmME9oU=4JZA9AX-f5BfKd_MeMH-k5_M+0fegBkhs4eiTMWhQ@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).