git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [Announce] libgit2 v0.17.0

From
Junio C Hamano <gitster@pobox.com>
Date
May 23, 2012, 16:51 UTC
Message-ID
<7v8vgi263h.fsf@alter.siamese.dyndns.org>
In-Reply-To
<nngy5oi3o37.fsf@transit.us.cray.com>
<dag@cray.com> writes:
Show 10 quoted lines
> 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.

Previous: dag@cray.comNext: Vicent Marti
Message 3 of 4 in “[Announce] libgit2 v0.17.0”
  1. Vicent MartiMay 19, 2012
  2. dag@cray.comMay 23, 2012
  3. Junio C HamanoMay 23, 2012
  4. Vicent MartiMay 24, 2012

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.