Re: Patch to integrate Metux MPM into the Debian unstable Apache2 tree

--5mCyUwZo2JvN/JJP
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Fri, Feb 25, 2005 at 04:56:43PM +0000, Thom May wrote:
> I'm strongly opposed to doing this. I see no sign that the metux authors
> have any desire to integrate metux with upstream, and I absolutely think
> that the apache2 package should not contain any major components that are=
n't
> included in the upstream tarball. (That way we're not exposed to the
> nightmare of multiple updates that the 1.3 package can be)
Hello Thom,

Having read your mail, I agree with your opinion that the Debian apache2
package should remain largely untainted.

There have been a few abortive attempts by the Metux MPM community to
increase awareness of the Metux MPM, but admittedly these have generally
stopped short of doing any extra work in order to justify inclusion into
the Apache 2 tree.

Do you have any suggestions as to how Metux MPM could increase the
chances of inclusion into mainstream Apache 2?

Thank you,

--=20

Nick Maynard
[email protected]

"It is always difficult for a man to grasp that a woman can love him=20
passionately without making the slightest effort to please him."=20
-- Anthony Powell

--5mCyUwZo2JvN/JJP
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQFCIz5qlgdIinVJTuARAk9OAJ97056BMZOgwxcMWF1pfQD8vA9EDwCgknLj
9lUH+M5nLSfxWX11lrvLr0A=
=ST6I
-----END PGP SIGNATURE-----

--5mCyUwZo2JvN/JJP--