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
Date:	Fri, 20 Sep 2002 18:06:43 -0400
From:	Christopher Faylor <cgf AT redhat DOT com>
To:	cygwin-developers AT cygwin DOT com
Subject:	Re: Issue with cygwin_daemon merge
Message-ID:	<20020920220643.GC30107@redhat.com>
Reply-To:	cygwin-developers AT cygwin DOT com
Mail-Followup-To:	cygwin-developers AT cygwin DOT com
References:	<00dd01c260e3$7dc35070$6132bc3e AT BABEL> <20020920203029 DOT GA29020 AT redhat DOT com> <010701c260e7$b7be0230$6132bc3e AT BABEL>
Mime-Version:	1.0
In-Reply-To:	<010701c260e7$b7be0230$6132bc3e@BABEL>
User-Agent:	Mutt/1.4i

On Fri, Sep 20, 2002 at 09:53:04PM +0100, Conrad Scott wrote:
>> Otherwise putting them in include/cygwin is ok.
>
>Thanks: it sounds like this is the way to go.  I'm not clear if/how I
>can produce a patch that moves files: is it possible?
>
>Or would it be okay for me to go ahead and make the change in HEAD
>myself?  The change involves moving the relevant files and editing both
>them and a couple of the cygserver* files that include them.

Yes, go ahead with this.  These files all fall within your maintainership
so I'm actually being consistent (and not even foolishly consistent) here,
I think.

cgf

- Raw text -