Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cocoon-dev@xml.apache.org
Content-Type: text/plain;
  charset="koi8-r"
From: Ivan Mikushin <ivan@openmechanics.net>
Organization: OpenMechanics.net
To: cocoon-dev@xml.apache.org
Subject: don't you want a bug fixed? I've even submitted a patch!
Date: Wed, 13 Nov 2002 12:59:31 +0500
User-Agent: KMail/1.4.3
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Message-Id: <200211131259.31732.ivan@openmechanics.net>

Dear Cocoon developers,

I want to discuss fixing some strange behaviour that I'm confident is a b=
ug.=20
I've already posted to this list but there was no reply: that's okay, I'v=
e=20
just went into the source code and fixed the thing myself. But don't you =
wish=20
to accept my contribution as a patch? See bug report at=20
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3D14245

Okay, I've been ignorant and haven't submit my patch apropriately for the=
=20
first time, but I'm learning and have already fixed the bug report to be=20
compliant with your standard. Though, it didn't even show in the auto pat=
ch=20
queue! (maybe that's because of the oddities of the patch queue=20
autogeneration)

I think Cocoon is a great project, and I'm using the CVS HEAD version in=20
production because I'm sure its pretty stable (I'm not using all the cutt=
ing=20
edge features though). And it really works great (except for that little=20
problem that I've reported and fixed)! And I (and sure you either) want i=
t to=20
continue to work fine and to improve stability.

Regards,

Ivan Mikushin,
OpenMechanics.net


---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org