This is the mail archive of the
cygwin-developers@cygwin.com
mailing list for the Cygwin project.
Re: Cygdaemon - planning
On Mon, 30 Jun 2003, Christopher Faylor wrote:
> On Mon, Jun 30, 2003 at 02:23:28PM +0100, Elfyn McBratney wrote:
> >On Thu, 26 Jun 2003, Christopher Faylor wrote:
> >
> >> I read Elfyn's reply as saying that the layout would stay intermixed with the
> >> cygwin directory. I think I've tried to fight this battle before and grudgingly
> >> accepted that cygdaemon lives in the cygwin directory. I thought that if we
> >> were moving things around I could maybe get things organized the way I'd
> >> like them. Guess not.
> >
> >I'm testing, tweaking and improving my heap implementation. I'll have it
> >finished this evening. Before I send the patch, should I shuffle the cygdaemon
> >stuff around into it's own directory?
>
> I'd prefer one patch for one thing.
>
> If you want, I can make the changes in CVS, "moving" whatever files you tell me
> to a new directory.
>
> cgf
OK, hows this?
winsup/cygwin/
cygserver.cc -> winsup/cygdaemon/cygdaemon.cc
cygserver_client.cc -> `` ''/client.cc
cygserver_ipc.h -> `` ''/cygdaemon_ipc.h
cygserver_process.cc -> `` ''/cygdaemon_process.cc
cygserver_shm.cc -> `` ''/cygdaemon_shm.cc
cygserver_shm.h -> `` ''/cygdaemon_smh.h
cygserver_transport.cc -> `` ''/transport.cc
cygserver_transport_pipes.cc -> `` ''/transport_pipes.cc
cygserver_transport_sockets.cc -> `` ''/transport_sockets.cc
With winsup/cygwin/{ipc,sem,shm}.cc left asis. ?
Elfyn
--