X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org Date: Fri, 5 Nov 2010 10:19:17 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: Cygwin paths in mingw64 Message-ID: <20101105141917.GC22365@ednor.casa.cgf.cx> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <30139174.post@talk.nabble.com> <285084.61145.qm@web25502.mail.ukl.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On Fri, Nov 05, 2010 at 01:31:15PM +0000, NightStrike wrote: >On Fri, Nov 5, 2010 at 8:44 AM, Marco Atzeri wrote: >> and Atlas is so deep unix related, that is better to use > >Does this imply that a direct mingw port is not feasible without >extensive effort? Can we terminate this discussion now? It hasn't really been on-topic for some time and speculation about whether a mingw port is feasible is really not fodder for this mailing list. cgf -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple