From: cmn@elego•de (Carlos Martín Nieto)
To: Nicolas Sebrecht <nicolas.s.dev@gmx•fr>
Cc: Vicent Marti <vicent@github•com>, Andreas Ericsson <ae@op5•se>,
greened@obbligato•org, git@vger•kernel.org
Subject: Re: libgit2 status
Date: Sun, 26 Aug 2012 00:32:35 +0200 [thread overview]
Message-ID: <87y5l2eh6k.fsf@centaur.cmartin.tk> (raw)
In-Reply-To: <20120825214614.GA8697@vidovic> (Nicolas Sebrecht's message of "Sat, 25 Aug 2012 23:46:15 +0200")
Nicolas Sebrecht <nicolas.s.dev@gmx•fr> writes:
> The 25/08/12, Vicent Marti wrote:
>
>> The development of libgit2 happens 100% in the open. I don't know what
>> "commercial entity" are you talking about, but there are several
>> companies and independent contributors working on the Library at the
>> moment.
>
> Right but as far as I'm aware of Junio had reserves about libgit2
> integration into git due to issues making repositories broken. Though,
The comment I saw about that was that at one point libgit2 had produced
broken trees; which is true, the algorithm for the almost-alphanumeric
sorting was slightly broken. This was fixed quite some time ago, which
he also mentioned in the same message.
> [ I'm somewhat in the same situation of OP. ]
If you wait for it to be perfect, it's never going to happen. If your
application would benefit, port it to libgit2 and report the issues you
find. That's the only way we can know of the odd edge cases and
improvements that we should make.
Note that the GitHub apps for Mac and Windows both use the Library to
perform parts of their job. Their new backend for the website is also
(going to be) based on libgit2.
I am also working on a project for a client involving the Library for
importing data and the only problem we've had is that we discovered an
edge case regarding symlinks and an assumption that one of the bindings
made wrt diffs, which is getting fixed.
cmn
next prev parent reply other threads:[~2012-08-25 22:33 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-24 14:02 libgit2 status greened
2012-08-25 9:56 ` Andreas Ericsson
2012-08-25 20:46 ` Vicent Marti
2012-08-25 21:46 ` Nicolas Sebrecht
2012-08-25 22:32 ` Carlos Martín Nieto [this message]
2012-08-26 7:26 ` Elia Pinto
2012-08-26 18:28 ` Junio C Hamano
2012-08-26 18:56 ` Junio C Hamano
2012-08-27 16:13 ` dag
2012-08-27 17:10 ` Junio C Hamano
2012-08-27 18:49 ` dag
2012-08-27 19:44 ` Junio C Hamano
2012-08-27 21:21 ` dag
2012-08-27 21:40 ` Nicolas Sebrecht
2012-08-28 17:59 ` dag
2012-08-28 18:36 ` Junio C Hamano
2012-10-19 0:42 ` Thiago Farina
2012-10-19 3:54 ` Ramkumar Ramachandra
2012-10-19 20:13 ` Junio C Hamano
2012-10-19 22:11 ` dag
2012-10-19 22:43 ` Junio C Hamano
2012-10-20 1:21 ` Thiago Farina
2012-10-20 7:58 ` Andreas Ericsson
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=87y5l2eh6k.fsf@centaur.cmartin.tk \
--to=cmn@elego$(echo .)de \
--cc=ae@op5$(echo .)se \
--cc=git@vger$(echo .)kernel.org \
--cc=greened@obbligato$(echo .)org \
--cc=nicolas.s.dev@gmx$(echo .)fr \
--cc=vicent@github$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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