> The list is
> included below
and yet, I forgot to include it:
1-: clang static analyser
2-: lldb
3-: klee
4-: safecode
5-: googletest
6-: valgrind (with gdb and kgdb plugins)
7-: coccinelle
8-: sparse
9-: kcov & gcov
10-: kasan & ubsan
11-: kernel memleaks detectors
12-: linux kernel
> > You only have to look at the past few attempts (scrapped versions)
> > to release apache to see the dangers in rush rush rush attitude.
>
> I’m assuming it’s a given that httpd should only release when ready
> to. I don’t think any of the release-often advocates are suggesting
> taking less
On Mon, Nov 12, 2018 at 1:26 AM Ruediger Pluem wrote:
>...
> The discussion died a little bit, because of the other issue (frequent
> writeev calls).
> I know that the liveprops issue is not fixed yet, but I guess it makes
> sense
> if you commit the patch you posted here already.
>
My time has
On 10/18/2018 01:45 PM, Joe Orton wrote:
> On Thu, Oct 18, 2018 at 11:09:13AM +0200, Ruediger Pluem wrote:
>> On 10/17/2018 07:47 PM, Joe Orton wrote:
>>> On Wed, Oct 17, 2018 at 03:32:34PM +0100, Joe Orton wrote:
I see constant memory use for a simple PROPFIND/depth:1 for the
That's contrary to how most see it, I held off replying to this thread because
I wanted to put this out there, on our system admin group, which contains some
491 members from 29 countries, and includes some of the rather well known ISP
and Hosting providers that are a lot bigger than a few
On Fri, Nov 9, 2018 at 6:05 PM Barry Pollard
wrote:
>
> 2/ it gives impression of immature and buggy software - this gives
> thoughts towards alternatives, IRC shows many admins have no loyalty
> todays much of todays software (well, windows fanbois excepted.
>
>
> Massively disagree.
