Date: Sun, 12 Feb 2012 12:41:18 -0800 From: Steve Kargl <sgk@troutmask.apl.washington.edu> To: Andriy Gapon <avg@FreeBSD.org> Cc: freebsd-ports@FreeBSD.org, Chris Rees <utisoft@gmail.com> Subject: Re: Please test your commits Message-ID: <20120212204118.GA86775@troutmask.apl.washington.edu> In-Reply-To: <4F3820AD.4090702@FreeBSD.org> References: <20120212193927.GA86426@troutmask.apl.washington.edu> <CADLo83_UZR0K15LQWoXb-AAhd1wj25fbeKSAPch5ji_Q=41f8A@mail.gmail.com> <20120212201624.GA86650@troutmask.apl.washington.edu> <4F3820AD.4090702@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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. -- Steve
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120212204118.GA86775>