Thread (1 message) 1 message, 1 author, 2016-06-15

Re: [PATCH 3/4] bisect: simplify the add of new bisect terms

From: Junio C Hamano <hidden>
Date: 2016-06-15 23:05:14

Matthieu Moy [off-list ref] writes:
Louis-Alexandre Stuber [off-list ref] writes:
quoted
quoted
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....
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help