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.
第九十九条 人民警察询问被侵害人或者其他证人，可以在现场进行，也可以到其所在单位、住处或者其提出的地点进行；必要时，也可以通知其到公安机关提供证言。
，详情可参考搜狗输入法2026
「目前仍未肯定美國當局會否上訴，感到有點擔心。」
当时，英伟达股价一度下跌近 17%，瞬间蒸发 6000 亿美元。