Mailing-List:	contact cygwin-developers-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-developers-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin-developers/>
List-Post:	<mailto:cygwin-developers AT cygwin DOT com>
List-Help:	<mailto:cygwin-developers-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-developers-owner AT cygwin DOT com
Delivered-To:	mailing list cygwin-developers AT cygwin DOT com
From:	"Robert Collins" <robert DOT collins AT syncretize DOT net>
To:	"'Conrad Scott'" <Conrad DOT Scott AT dsl DOT pipex DOT com>,
	<cygwin-developers AT cygwin DOT com>, <cygwin-apps AT cygwin DOT com>
Cc:	"'Nicholas Wourms'" <nwourms AT netscape DOT net>
Subject:	RE: Improved (?) cygserver available
Date:	Sat, 29 Jun 2002 07:55:39 +1000
Message-ID:	<001901c21eee$8aadf060$0200a8c0@lifelesswks>
MIME-Version:	1.0
X-Priority:	3 (Normal)
X-MSMail-Priority:	Normal
Importance:	Normal
X-MimeOLE:	Produced By Microsoft MimeOLE V6.00.2600.0000
In-Reply-To:	<00f401c21ed8$a1463fa0$6132bc3e@BABEL>

Conrad, 
	would you like to take maintenance of the cygserver over? I'm
not wure when I'll have enough time to do a responsive job of reviewing
patches. As you are interested and working on the main code plus the
SysVIPC, it's seems a small step to being maintainer. Maintainer
entails: bugfixing the cygserver and related code, gatewaying cygserver
patches into HEAD (whether from branches or just emails to
cygwin-patches), and finding a replacement before you stop being
maintainer :}.

I'm not stepping out of cygwin at all - just facing some serious time
constraints. IOW I'll still be able to help if you need extra input into
the cygserver, and will probably still comment on changes after the fact
:}.

Chris, would this be ok with you?

Rob

- Raw text -