From: Junio C Hamano <gitster@pobox.com>
To: <dag@cray.com>
Cc: Vicent Marti <vicent@github.com>, <libgit2@librelist.org>,
<git-dev@github.com>, <git@vger.kernel.org>
Subject: Re: [Announce] libgit2 v0.17.0
Date: Wed, 23 May 2012 09:51:46 -0700 [thread overview]
Message-ID: <7v8vgi263h.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <nngy5oi3o37.fsf@transit.us.cray.com> (dag@cray.com's message of "Wed, 23 May 2012 10:37:48 -0500")
<dag@cray.com> writes:
> Vicent Marti <vicent@github.com> writes:
>
>> Hello everyone,
>>
>> A new libgit2 release is here. This one is huge (most new features to
>> date). Check out the diff API. It's shiny.
>
> This is cool. I've wanted this for a while. How do you ensure that the
> operation of libgit2 matches that of git proper? Is there any plan to
> slowly convert git commands over to a libgit2 implementation?
There is no "plan" in the "concrete timeline and implementation strategy"
sense, but it is what any sane person would hope is a good longer-term
direction.
But it is also a bit of a chicken and an egg problem.
I am hoping that the library would become solid enough to allow us to
start attempting such an experiment some day, but at the same time, I know
that that "some day" is not in a very near future, after having seen at
$DAYJOB that a certain internal tool linked with a version of libgit2
breaking user's trees from time to time, bugs against the internal tool
getting filed and then some of them getting fixed at libgit2 level, either
by upstreaming fix or by updating to newer snapshot of libgit2.
next prev parent reply other threads:[~2012-05-23 16:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-19 0:00 [Announce] libgit2 v0.17.0 Vicent Marti
2012-05-23 15:37 ` dag
2012-05-23 16:51 ` Junio C Hamano [this message]
2012-05-24 1:57 ` Vicent Marti
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=7v8vgi263h.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=dag@cray.com \
--cc=git-dev@github.com \
--cc=git@vger.kernel.org \
--cc=libgit2@librelist.org \
--cc=vicent@github.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).