DigitalPrintPrint + Digital
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.
，这一点在新收录的资料中也有详细论述
Россия вышла из соглашения с ООН14:29
在地方工作时，习近平同志就多次向身边同志谈及谷文昌的故事，表示“谷文昌之所以一直受到广大干部群众的敬仰，是因为他在任时不追求轰轰烈烈的‘显绩’，而是默默无闻地奉献”“这种‘潜绩’是最大的‘显绩’。我们常讲的金杯银杯，不如老百姓的口碑；金奖银奖，不如老百姓夸奖，说的就是这个道理”。