Timo Sirainen wrote:
On Tue, 2009-01-27 at 14:20 -0600, Eric Rostetter wrote:
Quoting Timo Sirainen :
I've already written some unit tests in src/tests/. I don't really care
if you continue them the way I started or use some other toolset. And
What branch(es) should I write the
On Tue, 2009-01-27 at 14:20 -0600, Eric Rostetter wrote:
> Quoting Timo Sirainen :
>
> > I've already written some unit tests in src/tests/. I don't really care
> > if you continue them the way I started or use some other toolset. And
>
> What branch(es) should I write them for (1.0, 1.1, and/or
Quoting Timo Sirainen :
I've already written some unit tests in src/tests/. I don't really care
if you continue them the way I started or use some other toolset. And
What branch(es) should I write them for (1.0, 1.1, and/or 1.2). If multiple
branches, which is most important?
unless someone
As someone once pointed out to me when I was on a jihad for
error-checking/returning in a code development project, it's the things
that you *know* might break that you can slow down your code by putting
RC evals (evals are always very, very slow) to report on, but you
generally check for them
On Tue, 2009-01-27 at 11:21 -0600, Eric Rostetter wrote:
> Quoting Timo Sirainen :
>
> > Something automated. There are several different testing
> > possibilities actually. Unit tests is one thing.
>
> Last time I brought this up, it lead to so much endless arguing/debate
> over what type of t
Quoting Timo Sirainen :
Something automated. There are several different testing
possibilities actually. Unit tests is one thing.
Last time I brought this up, it lead to so much endless arguing/debate
over what type of testing to use, what toolset to use, etc. that nothing
ever happened.
I'd
Timo Sirainen wrote:
http://dovecot.org/releases/1.1/dovecot-1.1.10.tar.gz
http://dovecot.org/releases/1.1/dovecot-1.1.10.tar.gz.sig
v1.1.9 wasn't such a great release. Once again: Would be great if
someone started a proper testing suite so releases could be tested..
- Maildir: Keyword
On Jan 26, 2009, at 10:36 PM, Bruce Bodger wrote:
On Jan 26, 2009, at 6:32 PM, Timo Sirainen wrote:
http://dovecot.org/releases/1.1/dovecot-1.1.10.tar.gz
http://dovecot.org/releases/1.1/dovecot-1.1.10.tar.gz.sig
Timo:
Did you get around to modifying deliver wherein the '-e' has become
de
On Jan 26, 2009, at 6:32 PM, Timo Sirainen wrote:
http://dovecot.org/releases/1.1/dovecot-1.1.10.tar.gz
http://dovecot.org/releases/1.1/dovecot-1.1.10.tar.gz.sig
Timo:
Did you get around to modifying deliver wherein the '-e' has become
default behavior... per the earlier discussion?
B. B
Timo Sirainen wrote:
http://dovecot.org/releases/1.1/dovecot-1.1.10.tar.gz
http://dovecot.org/releases/1.1/dovecot-1.1.10.tar.gz.sig
v1.1.9 wasn't such a great release.
I refreshed the ManageSieve patch for v1.1:
http://www.rename-it.nl/dovecot/1.1/dovecot-1.1.10-managesieve-0.10.5.diff.gz
h
On Jan 26, 2009, at 7:49 PM, Robert Schetterer wrote:
Timo Sirainen schrieb:
v1.1.9 wasn't such a great release. Once again: Would be great if
someone started a proper testing suite so releases could be tested..
what you mean with testing suite exactly ?
some code stuff or a bunch of differe
Timo Sirainen schrieb:
> http://dovecot.org/releases/1.1/dovecot-1.1.10.tar.gz
> http://dovecot.org/releases/1.1/dovecot-1.1.10.tar.gz.sig
>
> v1.1.9 wasn't such a great release. Once again: Would be great if
> someone started a proper testing suite so releases could be tested..
what you mean wit
12 matches
Mail list logo
