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.
Даниил Иринин (Редактор отдела «Наука и техника»)
，推荐阅读safew官方版本下载获取更多信息
这正是长远政绩观的生动体现：“一张好的蓝图，只要是科学的、切合实际的、符合人民愿望的，就要像接力赛一样，一棒一棒接着干下去。”，详情可参考下载安装 谷歌浏览器 开启极速安全的 上网之旅。
Мерц резко сменил риторику во время встречи в Китае09:25