Please test your commits

Andriy Gapon avg at
Sun Feb 12 20:48:38 UTC 2012

on 12/02/2012 22:41 Steve Kargl said the following:
> On Sun, Feb 12, 2012 at 10:27:25PM +0200, Andriy Gapon wrote:
>> on 12/02/2012 22:16 Steve Kargl said the following:
>>> You seem to have the faulty belief that this is the first occurence
>>> of this type of issue?
>> So instead of proper report to the port's maintainer (including description of
>> your environment, possibly full build log, etc), possibly with a CC here, you
>> decided to vent out here...
>> Is there any requirement that people do the former and not the latter? :-)
> I'm not venting.  I'm simply requesting that all committers
> test the code that they intend to commit.  It is quite
> clear that this particular commit was not tested.
> The environment is irrelevant because malloc.h was poisoned
> 10 years, 3 months ago.  As to a full build log, the 
> necessary information was included in my original email.

Right, of course, sure.  Modern software projects all consist of a handful of C
files and a trivial makefile.  No autotools or other makefile generators.  No
bugs in them, etc.

Andriy Gapon

More information about the freebsd-ports mailing list