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.
六、免去李健、饶晓燕（女）、吴峰、黄自耀、楼缙东、张辅伦、黄河、蒋明军、孙聂娟（女）、孔立明、米于、王晓如（女）、徐燕如、杨学秋（女）、禹海波、袁晓贞（女）、张振的最高人民法院审判员职务。
。关于这个话题，WPS官方版本下载提供了深入分析
据多方消息，本次发布有望带来多款入门级产品的更新。
Фото: Mindaugas Kulbis / AP