admin管理员组文章数量:1391981
A commit object usually looks something like this:
tree aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
parent aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
author Somebody <[email protected]> 1741933308 +0000
committer Somebody <[email protected]> 1741933308 +0000
gpgsig -----BEGIN SSH SIGNATURE-----
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAA=
-----END SSH SIGNATURE-----
Title
Message message message message
message message message message
Is there any guarantee that the fields will be in this
- tree
- parent(s)
- author
- comitter
- gpgsig
order?
Apparently Git itself rejects commits where I reorder some fields (it doesn't let them pass fsck). However, is there any guarantee anywhere that this behavior will be kept?
本文标签:
版权声明:本文标题:Is there any guarantee that a Git commit object will have its fields stored in the treeparentsauthorcomittergpgsig order? - Stac 内容由网友自发贡献,该文观点仅代表作者本人, 转载请联系作者并注明出处:http://www.betaflare.com/web/1744670775a2618808.html, 本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。如发现本站有涉嫌抄袭侵权/违法违规的内容,一经查实,本站将立刻删除。
发表评论