<dag@xxxxxxxx> writes: > Vicent Marti <vicent@xxxxxxxxxx> 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. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html