[prev in list] [next in list] [prev in thread] [next in thread] 

List:       rpm-devel
Subject:    Re: [CVS] RPM: rpm-4_5: rpm/ CHANGES configure.ac rpm/rpmio/
From:       Per_Øyvind_Karlsen <pkarlsen () rpm5 ! org>
Date:       2009-03-18 22:04:30
Message-ID: 534660c60903181504p26683166t32b2d15e01aebca0 () mail ! gmail ! com
[Download RAW message or body]

2009/3/18 Michael Jennings <mej@kainx.org>

> On Wednesday, 18 March 2009, at 22:41:35 (+0100),
> Per ?yvind Karlsen wrote:
>
> > Actually it was, what I wanted was to make it optional and disabled
> > (something which obviously wasn't tested/cared for to begin with) by
> > default, so since I didn't enable it, it worked just fine for me.
> > I assume 'dmalloc' left there is what you're referring to, I've already
> > fixed it, I dunno what you're getting at with "This, too" though..
>
> I guess I should've said "sufficiently tested."  But testing the
> default case and nothing else really shouldn't meet anyone's
> definition of "tested."

Yeah, gosh, testing enabling/disabling of non-standard features at build
time which actually should disabled by default, introduced in sloppy fashio=
n
breaking for anyone not using it and that also requires stuff I don't even
have installed  is of course among top priorities of mine to fully test
before making one of many commits I have in queue..

Silly mistakes in commits are easy to detect and fix, I'd rather do more
testing once I'm done with what I'm working on rather than doing extensive
testing for each and every commit. It was only commited to cvs and easy to
fix there, it's not like it was anything released as stable to the world..
Silly mistakes in code commited are allowed and expected every now and then=
,
getting anal about it is just silly.

--
Regards,
Per =D8yvind

[Attachment #3 (text/html)]

<div class="gmail_quote">2009/3/18 Michael Jennings <span dir="ltr">&lt;<a \
href="mailto:mej@kainx.org">mej@kainx.org</a>&gt;</span><br><blockquote \
class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt \
0pt 0.8ex; padding-left: 1ex;"> On Wednesday, 18 March 2009, at 22:41:35 (+0100),<br>
<div class="im">Per ?yvind Karlsen wrote:<br>
<br>
&gt; Actually it was, what I wanted was to make it optional and disabled<br>
&gt; (something which obviously wasn&#39;t tested/cared for to begin with) by<br>
&gt; default, so since I didn&#39;t enable it, it worked just fine for me.<br>
&gt; I assume &#39;dmalloc&#39; left there is what you&#39;re referring to, I&#39;ve \
already<br> &gt; fixed it, I dunno what you&#39;re getting at with &quot;This, \
too&quot; though..<br> <br>
</div>I guess I should&#39;ve said &quot;sufficiently tested.&quot;  But testing \
the<br> default case and nothing else really shouldn&#39;t meet anyone&#39;s<br>
definition of &quot;tested.&quot;</blockquote><div>Yeah, gosh, testing \
enabling/disabling of non-standard features at build time which actually should \
disabled by default, introduced in sloppy fashion breaking for anyone not using it \
and that also requires stuff I don&#39;t even have installed  is of course among top \
priorities of mine to fully test before making one of many commits I have in \
queue..<br> <br>Silly mistakes in commits are easy to detect and fix, I&#39;d rather \
do more testing once I&#39;m done with what I&#39;m working on rather than doing \
extensive testing for each and every commit. It was only commited to cvs and easy to \
fix there, it&#39;s not like it was anything released as stable to the world..<br> \
</div></div>Silly mistakes in code commited are allowed and expected every now and \
then, getting anal about it is just silly.<br><br>--<br>Regards,<br>Per Øyvind<br>


______________________________________________________________________
RPM Package Manager                                    http://rpm5.org
Developer Communication List                        rpm-devel@rpm5.org

[prev in list] [next in list] [prev in thread] [next in thread]