Which code and how much code do the original Git codebase and libgit2 have in common (from nothing to all Git functionality except of command line client entry points)?
I'm primarily interested in how "stable" libgit2 is and how easily and quickly bug-fixes and/or improvements from future development in the original Git codebase can be adopted by libgit2.
Libgit2 is a dependency-free implementation of Git, with a focus on having a nice API for use within other programs. You can find it at https://libgit2.org.
Git is a DevOps tool used for source code management. It is a free and open-source version control system used to handle small to very large projects efficiently. Git is used to tracking changes in the source code, enabling multiple developers to work together on non-linear development.
Distributed Version Control System: Git has a remote repository which is stored in a server and a local repository which is stored in the computer of each developer. This means that the code is not just stored in a central server, but the full copy of the code is present in all the developers' computers.
I believe currently they share no code. You might be interested in this thread on the main Git list¹ regarding a prospective "reimplementing" Git on top of libgit2
— with main Git maintainer (Junio C Hamano) chiming in.
In general, you might find these search results² interesting to inspect.
¹ The original link was pointing at GMANE's archive, but it's unfortunately down.
² The link to search results was this.
It currently shares no code and...
According to Russell Belfer:
When will core git be rewritten on top of libgit2...the answer is never. We serve different masters...
He lists some details to why in the talk that the quote was taken from: https://www.youtube.com/watch?v=4ZWqr6iih3s
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With