a commit git 参数是什么意思_git commit - Git中的Sign Off功能是什么？

这个问题有一些很好的答案。 我会尝试添加更多广泛的答案，即关于这些种类的行/标题/预告片在当前的实践中。 与其说是签名标题特别是(它不是唯一的)。

当前，标题或预告片(↑1)如“签字”(↑2)在Git和Linux等项目中实践，有效的结构化元数据提交。 这些都附加到提交消息的末尾，之后的“自由形式”(非结构化)部分消息的正文。这些是通常由a分隔的标记值(或键值)对冒号和空间(man git-interpret-trailers)。

就像我提到的那样，“签字”并不是当前实践中唯一的预告片。 看到例如这个提交，这与“肮脏的牛”有关：

mm: remove gup_flags FOLL_WRITE games from __get_user_pages()

This is an ancient bug that was actually attempted to be fixed once

(badly) by me eleven years ago in commit 4ceb5db9757a ("Fix

get_user_pages() race for write access") but that was then undone due to

problems on s390 by commit f33ea7f404e5 ("fix get_user_pages bug").

In the meantime, the s390 situation has long been fixed, and we can now

fix it by checking the pte_dirty() bit properly (and do it better). The

s390 dirty bit was implemented in abf09bed3cce ("s390/mm: implement

software dirty bits") which made it into v3.9. Earlier kernels will

have to look at the page state itself.

Also, the VM has become more scalable, and what used a purely

theoretical race back then has become easier to trigger.

To fix it, we introduce a new internal FOLL_COW flag to mark the "yes,

we already did a COW" rather than play racy games with FOLL_WRITE that

is very fundamental, and then use the pte dirty flag to validate that

the FOLL_COW flag is still valid.

Reported-and-tested-by: Phil "not Paul" Oester

Acked-by: Hugh Dickins

Reviewed-by: Michal Hocko

Cc: Andy Lutomirski

Cc: Kees Cook

Cc: Oleg Nesterov

Cc: Willy Tarreau

Cc: Nick Piggin

Cc: Greg Thelen

Cc: stable@vger.kernel.org

Signed-off-by: Linus Torvalds

除了上面的“签收”预告片外，还有：

“抄送”(被通知补丁)

“Acked-by”(由代码所有者承认，“对我来说很好”)

“评论”(已审核)

“报告和测试”(报告并测试了问题(我假设))

其他项目，例如Gerrit，有自己的标题和相关的意义。

请参阅：[https://git.wiki.kernel.org/index.php/CommitMessageConventions]

故事的道德启示

这是我的印象，虽然这是最初的动机特定元数据是一些法律问题(另一方面判断)答案)，这种元数据的实践已经超越了公正处理形成作者链的案件。

[↑1]：man git-interpret-trailers

[↑2]：这些有时也被称为“s-o-b”(缩写)。