summaryrefslogtreecommitdiff
path: root/Documentation/RelNotes/1.5.3.txt
diff options
context:
space:
mode:
authorLibravatar Junio C Hamano <gitster@pobox.com>2012-10-02 15:08:16 -0700
committerLibravatar Junio C Hamano <gitster@pobox.com>2012-10-02 15:08:16 -0700
commit9dad83be45003940968656cf7ea037851b0e7bfe (patch)
treecf86876d02bac0ab3e00186cc3919ff093db9089 /Documentation/RelNotes/1.5.3.txt
parentfsck: --no-dangling omits "dangling object" information (diff)
downloadtgif-9dad83be45003940968656cf7ea037851b0e7bfe.tar.xz
t1450: the order the objects are checked is undefined
When a tag T points at an object X that is of a type that is different from what the tag records as, fsck should report it as an error. However, depending on the order X and T are checked individually, the actual error message can be different. If X is checked first, fsck remembers X's type and then when it checks T, it notices that T records X as a wrong type (i.e. the complaint is about a broken tag T). If T is checked first, on the other hand, fsck remembers that we need to verify X is of the type tag records, and when it later checks X, it notices that X is of a wrong type (i.e. the complaint is about a broken object X). The important thing is that fsck notices such an error and diagnoses the issue on object X, but the test was expecting that we happen to check objects in the order to make us detect issues with tag T, not with object X. Remove this unwarranted assumption. Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'Documentation/RelNotes/1.5.3.txt')
0 files changed, 0 insertions, 0 deletions