Sylvain Wallez wrote:
>
> Carsten Ziegeler wrote:
>
> >Joerg Heinicke wrote:
> >
> >
>
>
> >>Shame on all of us ;) Maybe we all have to stand a beer to
> Carsten at
> >>next CocoonGetTogether as the release is rescued.
> >>
> >>
> >>
> >Yes, yes, yes! Hmm, let me think, we will have app
Carsten Ziegeler wrote:
Joerg Heinicke wrote:
Shame on all of us ;) Maybe we all have to stand a beer to
Carsten at next CocoonGetTogether as the release is rescued.
Yes, yes, yes! Hmm, let me think, we will have approx. 150 attendees
for two days, that makes 75 beers for me per day. I
Unico Hommes wrote:
>
> Exactly it. I have to plead guilty. It's not too bad though,
> I'd gladly buy Carsten a beer :-D
>
Actually this was a nice one. I had to look more than twice to
see that as well :) But, I just noted down the beer so I won't
forget it :)
Carsten
Joerg Heinicke wrote:
>
> > Yeah, the confusion with the memory bug was partly due to me. After
> > your original fix that still had a problem with the reader I
> > introduced the bug again when I tried to fix that.
>
> So the lastconsumer null test really works, you only broke it
> with your
> > By the way, in our part of the world, this is called "Simon
> > says". No
> > idea who "Simon" is.
> >
>
> And the dutch would say about that "Joost mag het weten" ("Only Joost
> knows" or more freely "God only knows", not implying Joost is God of
> course, any Joost that is) Joost is ju
Geoff Howard wrote:
>
> Sylvain Wallez wrote:
> > [this is really off-topic now]
> >
> > Thibault Cantegrel wrote:
> >
> >> Sylvain Wallez wrote:
> >
> >
> >
> >>> Bertrand explains a well known child group game in french-speaking
> >>> countries which is names "Jacques a dit", which
> tran
Joerg Heinicke wrote:
>
>
> On 11.02.2004 16:42, Unico Hommes wrote:
>
> > Yeah, the confusion with the memory bug was partly due to me. After
> > your original fix that still had a problem with the reader I
> > introduced the bug again when I tried to fix that.
>
> So the lastconsumer null
On 11.02.2004 16:42, Unico Hommes wrote:
Yeah, the confusion with the memory bug was partly due to me. After your
original fix that still had a problem with the reader I introduced the
bug again when I tried to fix that.
So the lastconsumer null test really works, you only broke it with your
rea
I'm a little unclear. Is the code frozen or melting? Will there be a
release this week? I hope so. I really want to pick up 2.1.4 for our
development.
Ralph
Sylvain Wallez wrote:
[this is really off-topic now]
Thibault Cantegrel wrote:
Sylvain Wallez wrote:
Bertrand explains a well known child group game in french-speaking
countries which is names "Jacques a dit", which translates to "Jack
said": you must do what follows "Jacques a dit", but must
Bertrand Delacretaz wrote:
Le Mercredi, 11 fév 2004, à 17:37 Europe/Zurich, Sylvain Wallez a écrit :
...I let you decide as I'm currently too swamped to follow closely
the flow...
What, Sylvain not following the flow? I thought you were a Flow expert
;-)
Actually, I meant "flood". Now, noti
[this is really off-topic now]
Thibault Cantegrel wrote:
Sylvain Wallez wrote:
Bertrand explains a well known child group game in french-speaking
countries which is names "Jacques a dit", which translates to "Jack
said": you must do what follows "Jacques a dit", but must absolutely
no do i
Memory Leak has gone.
Regards,
Michael
--
GMX ProMail (250 MB Mailbox, 50 FreeSMS, Virenschutz, 2,99 EUR/Monat...)
jetzt 3 Monate GRATIS + 3x DER SPIEGEL +++ http://www.gmx.net/derspiegel +++
Sylvain Wallez wrote:
Bertrand Delacretaz wrote:
Le Mercredi, 11 fév 2004, à 16:11 Europe/Zurich, Carsten Ziegeler a
écrit :
To increase the confusion :) I think we should stick to the code
freeze as I
see the chance for a release tomorrow...
A release would be good as it looks like all kn
Le Mercredi, 11 fév 2004, à 17:37 Europe/Zurich, Sylvain Wallez a écrit
:
...I let you decide as I'm currently too swamped to follow closely the
flow...
What, Sylvain not following the flow? I thought you were a Flow expert
;-)
-Bertrand
Bertrand Delacretaz wrote:
Le Mercredi, 11 fév 2004, à 16:11 Europe/Zurich, Carsten Ziegeler a
écrit :
To increase the confusion :) I think we should stick to the code
freeze as I
see the chance for a release tomorrow...
A release would be good as it looks like all known blockers are gone.
F
I have been eyeing it :-) because I think it is a major bug as well. But
I decided that I knew too little about the consequences of your fix to
apply it so shortly before the release.
So, unless another committer is willing to take the risk I would suggest
we postpone this one until after the rel
These are the bugs that are still open against the release:
25203 SQLTransformer: duplicate namespace declaration when serializing XML
26186 Memory Leak caused by cocoon:// protocol
26751 Cocoon gets web-app_2_2.dtd from flres.java.Sun.COM at startup
26753 [PATCH] Persistent store or cache corru
On 11 Feb 2004, at 17:10, Bertrand Delacretaz wrote:
We'll try this at the next GetTogether ;-)
Don't tempt me into thinking about the new edition already - I still
want to get something else done this year as well. ;-)
--
Steven Noelshttp://outerthought.org/
Outerth
On Wed, Feb 11, 2004 at 04:50:57PM +0100, Carsten Ziegeler wrote:
> Unico Hommes wrote:
> >
> > Yeah, the confusion with the memory bug was partly due to me.
> > After your original fix that still had a problem with the
> > reader I introduced the bug again when I tried to fix that.
> >
> > I
Le Mercredi, 11 fév 2004, à 16:11 Europe/Zurich, Carsten Ziegeler a
écrit :
To increase the confusion :) I think we should stick to the code
freeze as I
see the chance for a release tomorrow...
A release would be good as it looks like all known blockers are gone.
FYI I cannot help integrating t
Sorry to butt in guys :)
But I was wondering if anyone could commit the patch for bug 26854
(Flow redirecting)
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26854
I am pretty sure it will fix 26571, and maybe 25437 and 22132.
I am cvs illiterate, and can't figure out how to patch my own copy
Unico Hommes wrote:
>
> Yeah, the confusion with the memory bug was partly due to me.
> After your original fix that still had a problem with the
> reader I introduced the bug again when I tried to fix that.
>
> I agree that your latest fix should definitely work. In fact
> I took the opertun
Yeah, the confusion with the memory bug was partly due to me. After your
original fix that still had a problem with the reader I introduced the
bug again when I tried to fix that.
I agree that your latest fix should definitely work. In fact I took the
opertunity to install anteater and whereas b
To increase the confusion :) I think we should stick to the code freeze as I
see the chance for a release tomorrow.
As far as I see it, we have the vetos from Reinhard and Joerg (Vadim
revoked), and it seems that these vetos stand and fall with the memory leak
bug, so all we have to do is: fix the
25 matches
Mail list logo