Content-level diffs, three-way merge, and blame stay in libgit2 rather than being reimplemented in SQL, since libgit2 already has that support and works against the Postgres backends through cgo bindings. The Forgejo fork would be “replace modules/git with libgit2 backed by Postgres” rather than “replace modules/git with raw SQL,” because the read-side queries only cover the simple cases and anything involving content comparison or graph algorithms still needs libgit2 doing the work with Postgres as its storage layer. That’s a meaningful dependency to carry, though libgit2 is well-maintained and already used in production by the Rust ecosystem and various GUI clients. SQL implementations of some of this using recursive CTEs would be interesting to try eventually but aren’t needed to get a working forge. The remaining missing piece is the server-side pack protocol: the remote helper covers the client side, but a Forgejo integration also needs a server that speaks upload-pack and receive-pack against Postgres, either through libgit2’s transport layer or a Go implementation that queries the objects table directly.
Kevin Church/BBC News
。业内人士推荐快连下载安装作为进阶阅读
Reactor installed at UK's newest nuclear power station
withdrawal. Those are problems that, mercifully, could mostly be sorted out with
。heLLoword翻译官方下载对此有专业解读
Since they no longer have it, they are informed that they cannot access their backed up data. Goodbye, memories.
Александра Синицына (Ночной линейный редактор)，推荐阅读WPS下载最新地址获取更多信息