[[[ To any NSA and FBI agents reading my email: please consider ]]] [[[ whether defending the US Constitution against all enemies, ]]] [[[ foreign or domestic, requires you to follow Snowden's example. ]]]
> There is a point when there are enough changes (or it's sufficiently > unclear what function might be involved in the bug) that "git bisect" is a > better approach - remembering that you're looking at past changes to an > entity for some reason, likely to find what caused a particular bug. If you prefer that approach, it is already available. However, the point is not to eliminate the other non-git options that we support. > However, in C it's very rare for a change to a function's return type (a) > not to change anything else in the function and (b) at the same time, to > be the cause of a bug. That may be true, but the problem I am concerned with is that a change gets attributed to the previous entity. That's because GNU diff does only a rough approximation for finding the first and last line of an entity. It is good enough for other purposes but not for this one. I think it will not be very hard to make this completely dependable. -- Dr Richard Stallman President, Free Software Foundation (https://gnu.org, https://fsf.org) Internet Hall-of-Famer (https://internethalloffame.org)
