+2
−0
+1
−1
+6
−7
+19
−25
+17
−13
Loading
Gitlab 现已全面支持 git over ssh 与 git over https。通过 HTTPS 访问请配置带有 read_repository / write_repository 权限的 Personal access token。通过 SSH 端口访问请使用 22 端口或 13389 端口。如果使用CAS注册了账户但不知道密码,可以自行至设置中更改;如有其他问题,请发邮件至 service@cra.moe 寻求协助。
This changes behaviour of rte_update() and rte_update2(). Formerly, the caller of rte_update2() took care of caching rta and allocating rte; then rte_update2() freed the structures if it didn't use them. Now rte_update2() does the permanent/global copies of rte+rta itself. Allocation of rte+rta passed to rte_update2() is considered temporary and the caller is also responsible to free these structures properly. This is true for any kind of allocation: rte_update2() will always allocate its own copy of the data passed (either really or just by raising usecount in rta cache). It is now possible (and in many protocols now used) to allocate rte+rta on stack and pass them to rte_update(). It will deal with them correctly.
CRA Git | Maintained and supported by SUSTech CRA and CCSE