Matthieu Moy <Matthieu.Moy@xxxxxxxxxxxxxxx> writes: > 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 think both I and you misunderstood what they wanted to do, which is to write out good and bad into terms file even though these are not customized, and then always read from terms file to learn what words are used for good and bad. So from _that_ point of view, ENOENT is an error just like others. But I do not think it is a good idea to penalize the normal case by writing the terms file and reading them back from it when the user is bisecting with good/bad in the first place, so.... -- 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