Louis-Alexandre Stuber <stuberl@xxxxxxxxxxxxxxxxxxxxxxx> writes: >> That is very different from ENOENT, which is an expected error when >> you are not using a customized terms. > > But in the current state, we are going to create bisect_terms even if > the bisection is in bad/good mode. Which means that in normal cases, you'll either succeed to open it, or get ENOENT. We're talking about unexcepted cases (you don't have permission to read it because it's not your file, because you messed up with a chmod, or whatever reason). I don't expect a tool to consider that an unreadable file is equivalent to no file at all. If something's wrong, as a user, I expect a helpful message telling me what's wrong, to give me a clue on how to solve it. -- 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