如下图，可以查询历史补丁集的更多信息。
Further more information can be grabbed from the Patch history by clicking like below.
同一变更的所有后续提交都会关联到一个补丁集上。
This will allow all subsequent commits of the same change to be associated with the same patch set.
在早期的SELinux中，它还是一个补丁集，它提供了自己的安全性框架。
In the early days of SELinux, while it was still a set of patches, it provided its own security framework.
第一个数字是变更号的最后两位，第二个数字是变更号，第三个数字是补丁集号。
Although it's an implementation detail, the first digits are the last two digits of the change number, and second digits are the change number, and the third digits is the patch set number.
现在再去看Gerrit中的change1，你会发现出现了第二个与该变更相关联的补丁集。
If you now look in Gerrit at change 1 you'll see that there is a second patch set associated with the change.
猜测：是不是只是在云端托管数据库，但最终还是在数据库终端打补丁，因此做法跟普通数据库应用补丁集并没有太大区别？
Guess: Probably we host database in cloud but again at the end its database, hence have to apply patch like we do on-premises.?
猜测：是不是只是在云端托管数据库，但最终还是在数据库终端打补丁，因此做法跟普通数据库应用补丁集并没有太大区别？
Guess: Probably we host database in cloud but again at the end its database, hence have to apply patch like we do on-premises.?
应用推荐