From: "Rob McDonald" <robm@asdl.gatech.edu>
To: "Johannes Schindelin" <Johannes.Schindelin@gmx.de>
Cc: "Andreas Ericsson" <ae@op5.se>, <git@vger.kernel.org>
Subject: Re: Possibility of a MinGW version?
Date: Sun, 25 Dec 2005 12:16:29 -0500 [thread overview]
Message-ID: <003101c60976$f2912ff0$6900a8c0@sps> (raw)
In-Reply-To: Pine.LNX.4.63.0512241509240.24308@wbgn013.biozentrum.uni-wuerzburg.de
> Well, cygwin is everything but unmaintained. It's unfair to blaim the good
> work of the cygwin folks if you can't get it to work. I have *never* had a
> problem I could not solve with cygwin. In particular, *no* package got
> messed up when I installed/upgraded another package. Before you ask: I use
> cygwin extensively.
I'm sorry to have seemed harsh in my criticism. I have not used Cygwin
seriously in a couple years. At the time, as a user, I saw no noticable
progress. The project seemed dead. I always had trouble with their package
management program. I'm glad you've never had similar problems.
> As I already stated, there are two *big* showstoppers when it comes to
> port git to MinGW.
Thanks very much for those comments, that is exactly the kind of information
I was hoping to get out of this thread.
> Okay, I'll bite. Could you please port python to MinGW?
As I said, my experience porting apps to MinGW has been very limited in
scope. Essentially limited to programs that don't use any unixisms. I see
no need to port Python, they already have a native version. And, you could
always use Jython if they didn't.
> You're welcome. Just be sure to tackle the hard problems first, else you
> end up having wasted lots of valuable time for nothing.
Thanks for the insight. I didn't think the shell and / vs \ were going to
be the real issues.
Rob
next prev parent reply other threads:[~2005-12-25 17:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-24 2:34 Possibility of a MinGW version? Rob McDonald
2005-12-24 10:09 ` Andreas Ericsson
2005-12-24 10:18 ` Sven Verdoolaege
2005-12-24 10:24 ` Andreas Ericsson
2005-12-24 12:07 ` Johannes Schindelin
2005-12-24 16:40 ` David Brown
2005-12-24 13:51 ` Rob McDonald
2005-12-24 14:16 ` Johannes Schindelin
2005-12-25 17:16 ` Rob McDonald [this message]
2005-12-31 16:39 ` Christopher Faylor
2005-12-31 21:53 ` H. Peter Anvin
2006-01-01 5:25 ` Christopher Faylor
2005-12-31 16:40 ` Christopher Faylor
2005-12-24 17:58 ` Junio C Hamano
2005-12-24 23:44 ` Andreas Ericsson
2005-12-25 1:47 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='003101c60976$f2912ff0$6900a8c0@sps' \
--to=robm@asdl.gatech.edu \
--cc=Johannes.Schindelin@gmx.de \
--cc=ae@op5.se \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.