From: Brian Dessent <brian@dessent.net>
To: cygwin@cygwin.com
Subject: Re: Looking for new apache maintainer
Date: Thu, 27 May 2004 12:40:00 -0000 [thread overview]
Message-ID: <40B5BD6B.63A9DFD7@dessent.net> (raw)
In-Reply-To: <001101c443d0$dee51470$78d96f83@robinson.cam.ac.uk>
Max Bowsher wrote:
> > I hadn't planned to package 2.x because its native win32 version would
> > be significantly faster with a thread MPM than a Cygwin port. But I
> > suppose a Cygwin version would be useful if you wanted to test or
> > develop things that are destined for a 2.x/Unix machine. I also don't
> > know what's involved with compiling 2.x for Cygwin. Maybe after 1.x and
> > the modules are out...
>
> OK, my reason for asking was because I currently have apr and apr-util
> packages pending, so if anyone was to package Apache 2, I'd need to
> co-ordinate with them. I have actually got a working cygwin apache 2 to
> compile, but it was quite messy, and I have no time to tidy it up at the
> moment.
Ah, of course. I'll contact you before I start packaging 2.x, if ever.
Brian
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
next prev parent reply other threads:[~2004-05-27 10:05 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-26 11:38 Christopher Faylor
2004-05-27 8:19 ` Brian Dessent
2004-05-27 9:20 ` Christopher Faylor
2004-05-27 9:52 ` Max Bowsher
2004-05-27 10:05 ` Brian Dessent
2004-05-27 12:19 ` Max Bowsher
2004-05-27 12:40 ` Brian Dessent [this message]
2004-05-27 14:31 ` Andrew DeFaria
2004-05-27 14:43 ` Christopher Faylor
2004-05-27 15:13 ` Brian Dessent
2004-05-27 15:39 ` Andrew DeFaria
2004-05-27 16:09 ` Brian Dessent
2004-05-27 16:26 ` Christopher Faylor
2004-05-27 16:47 ` Igor Pechtchanski
2004-05-27 17:18 ` Christopher Faylor
2004-05-27 18:15 ` Brian Dessent
2004-05-28 11:26 ` Reini Urban
2004-05-27 21:25 ` Max Bowsher
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=40B5BD6B.63A9DFD7@dessent.net \
--to=brian@dessent.net \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).