哪些git命令执行完整性检查？
哪些git命令执行完整性检查？
提问于 2018-03-26 05:32:22
为了确定使用git-1.7.4.1在对象数据库中警告用户损坏的速度，我使用了一个单位开关：
$ git init repo
Initialized empty Git repository in /tmp/repo/.git/
$ cd repo
$ echo 'very important info' >critical
$ git add critical
$ git commit -m critical
[master (root-commit) c4d6d90] critical
1 files changed, 1 insertions(+), 0 deletions(-)
create mode 100644 critical
$ git ls-tree HEAD
100644 blob 82d423c32c4bb2c52938088e0234db041bf4eaaf critical
$ git show 82d423c32c4bb2c52938088e0234db041bf4eaaf
very important info
$ echo 'Very important info' | git hash-object --stdin -w
81a3797afe76d339db25c0f9c705a6caa47279c2
$ mv .git/objects/81/a3797afe76d339db25c0f9c705a6caa47279c2 \
.git/objects/82/d423c32c4bb2c52938088e0234db041bf4eaaf当然了!git-fsck告示
$ git fsck
error: sha1 mismatch 82d423c32c4bb2c52938088e0234db041bf4eaaf
error: 82d423c32c4bb2c52938088e0234db041bf4eaaf: object corrupt or missing
missing blob 82d423c32c4bb2c52938088e0234db041bf4eaaf但git-log对改变很满意
$ git log -p
commit c4d6d90467af9ffa94772795d5c5d191228933c1
Author: Greg Bacon <gbacon@dbresearch.net>
Date: Thu Apr 7 12:20:53 2011 -0500
critical
diff --git a/critical b/critical
new file mode 100644
index 0000000..82d423c
--- /dev/null
+++ b/critical
@@ -0,0 +1 @@
+Very important info原样git-checkout...
$ rm critical
$ git checkout .
$ cat critical
Very important info特定的调用git-show揭露腐败
$ git show 82d423c32c4bb2c52938088e0234db041bf4eaaf
error: sha1 mismatch 82d423c32c4bb2c52938088e0234db041bf4eaaf
fatal: bad object 82d423c32c4bb2c52938088e0234db041bf4eaaf但不是更广泛的。
$ git show
commit c4d6d90467af9ffa94772795d5c5d191228933c1
Author: Greg Bacon <gbacon@dbresearch.net>
Date: Thu Apr 7 12:20:53 2011 -0500
critical
diff --git a/critical b/critical
new file mode 100644
index 0000000..82d423c
--- /dev/null
+++ b/critical
@@ -0,0 +1 @@
+Very important info甚至于git-clone没注意到！
$ cd ..
$ git clone repo clone
Cloning into clone...
done.
$ cat clone/critical
Very important info具体的git命令模式的完整列表是什么(G.，，，git show $sha1应该在场但不在场git show或git show HEAD)执行完整性检查？
回答 2
Stack Overflow用户
发布于 2018-03-26 13:33:15
下面是我将如何找到这个结果，尽管我不打算遍历每个源文件来计算执行检查的条件。)
克隆git的源代码：
git clone git://git.kernel.org/pub/scm/git/git.git看看你关心的版本：
cd git
git checkout v1.7.1查找该错误消息：
git grep 'sha1 mismatch'这会导致你object.c而parse_object功能。现在查找该函数：
git grep parse_object然后检查38个文件，检查调用该函数的条件。
Stack Overflow用户
发布于 2018-03-26 15:19:21
Functions calling this function: parse_object
File Function Line
0 bundle.c verify_bundle 110 struct object *o = parse_object(e->sha1);
1 bundle.c create_bundle 242 struct object *object = parse_object(sha1);
2 bundle.c create_bundle 247 struct object *object = parse_object(sha1);
3 bundle.c create_bundle 323 obj = parse_object(sha1);
4 commit.c lookup_commit_reference_gently 30 struct object *obj = deref_tag(parse_object(sha1), NULL, 0);
5 http-backend.c show_text_ref 372 struct object *o = parse_object(sha1);
6 http-push.c one_remote_object 742 obj = parse_object(sha1);
7 http-push.c add_remote_info_ref 1530 o = parse_object(ref->old_sha1);
8 log-tree.c add_ref_decoration 93 struct object *obj = parse_object(sha1);
9 merge-recursive.c get_ref 1664 object = deref_tag(parse_object(sha1), name, strlen(name));
a pack-refs.c handle_one_ref 43 struct object *o = parse_object(sha1);
b pretty.c format_commit_one 835 parse_object(commit->object.sha1);
c reachable.c add_one_reflog_ent 122 object = parse_object(osha1);
d reachable.c add_one_reflog_ent 125 object = parse_object(nsha1);
e reachable.c add_one_ref 133 struct object *object = parse_object(sha1);
f reflog-walk.c fake_reflog_parent 234 commit_info->commit = (struct commit *)parse_object(reflog->osha1);
g refs.c peel_ref 647 o = parse_object(base);
h refs.c write_ref_sha1 1452 o = parse_object(sha1);
i remote.c ref_newer 1482 o = deref_tag(parse_object(old_sha1), NULL, 0);
j remote.c ref_newer 1487 o = deref_tag(parse_object(new_sha1), NULL, 0);
k revision.c add_head_to_pending 166 obj = parse_object(sha1);
l revision.c get_reference 176 object = parse_object(sha1);
m revision.c handle_commit 196 object = parse_object(tag->tagged->sha1);
n revision.c handle_one_reflog_commit 855 struct object *o = parse_object(sha1);
o server-info.c add_info_ref 12 struct object *o = parse_object(sha1);
p sha1_name.c peel_to_type 508 o = parse_object(sha1);
q sha1_name.c peel_to_type 511 if (!o || (!o->parsed && !parse_object(o->sha1)))
r sha1_name.c peel_onion 573 o = parse_object(outer);
s sha1_name.c peel_onion 578 if (!o || (!o->parsed && !parse_object(o->sha1)))
t sha1_name.c handle_one_ref 698 struct object *object = parse_object(sha1);
u sha1_name.c get_sha1_oneline 740 if (!parse_object(commit->object.sha1))
v tag.c deref_tag 16 o = parse_object(((struct tag *)o)->tagged->sha1);
w tree.c parse_tree_indirect 271 struct object *obj = parse_object(sha1);
x tree.c parse_tree_indirect 284 parse_object(obj->sha1);
y upload-pack.c got_sha1 342 o = parse_object(sha1);
z upload-pack.c reachable 382 parse_object(commit->object.sha1);
A upload-pack.c receive_needs 526 object = parse_object(sha1);
B upload-pack.c send_ref 644 struct object *o = parse_object(sha1);
C upload-pack.c mark_our_ref 670 struct object *o = parse_object(sha1);
D walker.c loop 182 parse_object(obj->sha1);页面原文内容由Stack Overflow提供。腾讯云小微IT领域专用引擎提供翻译支持
原文链接：
https://stackoverflow.com/questions/-100007785
复制相关文章
相似问题