Date: Thu, 25 Jan 2001 11:46:32 -0500
Message-Id: <200101251646.LAA27129@envy.delorie.com>
X-Authentication-Warning: envy.delorie.com: dj set sender to dj AT envy DOT delorie DOT com using -f
From: DJ Delorie <dj AT delorie DOT com>
To: djgpp-workers AT delorie DOT com
In-reply-to: <20010125090536.B19492@kendall.sfbr.org> (message from JT
	Williams on Thu, 25 Jan 2001 09:05:36 -0600)
Subject: Re: Adding MWDPMI sources to CVS
References: <Pine DOT OSF DOT 4 DOT 30 DOT 0101251122250 DOT 10291-100000 AT sirppi DOT helsinki DOT fi> <20010125090536 DOT B19492 AT kendall DOT sfbr DOT org>
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


> What are the reasons for organizing mwdpmi differently than cwsdpmi?

If Charles wanted cwsdpmi on my cvs server, I'd probably put it in
src/cwsdpmi too.  But, cwsdpmi is maintained elsewhere and the mwdpmi
folks asked if they could host it here.  So, my choices are either
keep it isolated from djgpp, or include it in djgpp, or put it in
djgpp's cvs but in a different module (like I do for the mini-faq) so
that at least cvs accounts are shared.