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.
Последние новости
，推荐阅读谷歌浏览器【最新下载地址】获取更多信息
延续飞傲的 Hi-Fi 基因：继承飞傲深厚的声学底蕴，提供纯净的 3.5mm 有线耳机输出，满足你对高解析音质的挑剔追求。
While the questions "might seem a little bit probing", no one was being "judged" and it was important to get honest answers to invest in the right services for the island, she added.