On 11/02/2014 8:58 p.m., Kinkie wrote:
Hi,
attached is the second part of Vector refactoring. It replaces
Vector with std::vector in all clients except for Stack, which I
believe to more sensible to replace with std::stack instead of
reimplementing.
Code has been farm-build-tested and
Hi all,
there are two topics I'd like us to discuss about to share an
agreement when the right time comes. I'm spreading the discussion over
two threads in order not to cross wires and facilitate discussion.
During recent discussion on IRC it was found out that there are not
that many big
Hi all,
there are two topics I'd like us to discuss about to share an
agreement when the right time comes. I'm spreading the discussion over
two threads in order not to cross wires and facilitate discussion.
The topic I'm thinking of is the policy of autoconf-detecting some
system headers we
I've had a strange assert (at HttpHeader.cc:1551, in
~HttpHeaderEntry), but I could not reproduce that nor find anything in
p2 or p3 of the refactor patch which may trigger it.
I'm running more tests at full debugging.
Hit it again. Looking at HttpHeader, that code is really crappy.
The root
Sigh.
Amos
Original Message
Subject: [CTTE #727708] Default init system for Debian
To: debian-devel-announce
The technical committee was asked in #727708 to decide which init
system would be the default init system for Debian. The decision is
below:
RESOLUTION
We
ons 2014-02-12 klockan 10:13 +1300 skrev Amos Jeffries:
Sigh.
Amos
Why sigh? systemd have worked well for me for years now.. except Squid..
For Squid the main impact is that we really should have a dont
daemonize yourself run mode which don't otherwise limit functionality.
The -N option we
On 2014-02-12 10:27, Henrik Nordström wrote:
ons 2014-02-12 klockan 10:13 +1300 skrev Amos Jeffries:
Sigh.
Amos
Why sigh? systemd have worked well for me for years now.. except
Squid..
For Squid the main impact is that we really should have a dont
daemonize yourself run mode which don't
ons 2014-02-12 klockan 10:47 +1300 skrev Amos Jeffries:
Exactly. More deep changes needed.
Well, systemd (and most other service monitors) do manage services that
background themselves as well, just not optimally. So it's more changes
desired, not strictly needed.
But seriously, it's a very
On 2014-02-12 11:07, Henrik Nordström wrote:
ons 2014-02-12 klockan 10:47 +1300 skrev Amos Jeffries:
Exactly. More deep changes needed.
Well, systemd (and most other service monitors) do manage services that
background themselves as well, just not optimally. So it's more changes
desired, not
On 02/11/2014 04:48 AM, Kinkie wrote:
The topic I'm thinking of is the policy of autoconf-detecting some
system headers we use. While this is undoubtably good for C- and
system- headers, it doesn't make much sense for pure C++ headers,
which are very strongly defined by the standard and for
On 2014-02-12 06:19, Kinkie wrote:
I've had a strange assert (at HttpHeader.cc:1551, in
~HttpHeaderEntry), but I could not reproduce that nor find anything in
p2 or p3 of the refactor patch which may trigger it.
I'm running more tests at full debugging.
Hit it again. Looking at HttpHeader,
On 02/11/2014 03:28 PM, Amos Jeffries wrote:
On 2014-02-12 06:19, Kinkie wrote:
I suspect that HttpHeader.cc needs some love. Has anyone already
thought about this topic or should I prepare a proposal? I'd like to
share design ideas before going for an implementation attempt.
Yes there is
On 2014-02-12 11:26, Alex Rousskov wrote:
On 02/11/2014 04:48 AM, Kinkie wrote:
The topic I'm thinking of is the policy of autoconf-detecting some
system headers we use. While this is undoubtably good for C- and
system- headers, it doesn't make much sense for pure C++ headers,
which are very
On 2014-02-12 04:45, Kinkie wrote:
Hi,
the attached patch is the missing piece of Vector refactoring: it
replaces users of Stack with std::stack (or std::vector, in one case
where it's needed due to also needing to iterate over the elements),
and removes Vector, Stack and related unit tests.
14 matches
Mail list logo
