Follow-up Comment #19, bug #15919 (project make):
I said all bugs would be reexamined before a release: I didn't say they would
all be fixed before a release. Bug 3330 _was_ looked at (by me) before 3.81
was released, but I thought it was bound up with the other issues surrounding
.SECONDARY and I elected not to spend time trying to fix it then. It appears
that I didn't look at it closely enough; if I'd been more diligent I would
have seen that it was something else. That was an error in judgment on my
part.
I'm sorry but I don't consider this bug critical enough to make a new release
for it alone. This issue has been in the code since at least GNU make 3.75
(that's the farthest back that I tested it) which is over 10 years old, and
in all that time as far as I can tell from searching the mailing lists, etc.
only yourself and J. David Bryan have run into it. That's not to say it's
not a bad bug: it is, and it will be fixed in 3.82. But as for an immediate
bug fix release, I don't think it's justified in this case. There are plenty
of instances where programs have bugs that crash or return incorrect results
on valid input, and an immediate release is not created for each of those.
The question is, how many people will the problem affect and what is the
impact of the bug (security flaw, erases a disk, etc.)? This bug simply
doesn't rise to the level needed to justify an emergency release to fix it,
in my opinion.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?15919>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
_______________________________________________
Bug-make mailing list
Bug-make@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-make
