Axel Bonnet <axel.bonnet@xxxxxxxxxxxxxxx> writes: > +test_expect_success 'blame with --no-textconv' ' > + git blame --no-textconv one.bin | grep Number2 >blame > + find_blame <blame >result > + test_cmp expected result > +' Don't you want to add && at each end of line, to make sure you catch potential failures of git blame on the first line (e.g. git blame producing the correct output and then segfaulting for example)? Actually, to really catch such failures, you should not run git on the left hand side of a | (otherwise, you look for failures of the right hand side), and do this instead: test_expect_success 'no filter specified' ' git blame one.bin >to-grep && grep Number2 to-grep >blame && find_blame <blame >result && test_cmp expected result ' -- Matthieu Moy http://www-verimag.imag.fr/~moy/ -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html