From: "Nguyen Thai Ngoc Duy" <pclouds@gmail.com>
To: "Git Mailing List" <git@vger.kernel.org>
Subject: [WIP] Get rid of msys in favor of busybox port for windows
Date: Tue, 10 Jul 2007 11:32:00 -0400 [thread overview]
Message-ID: <fcaeb9bf0707100832j3c2ff076gab5c9bd4f9d3f4a0@mail.gmail.com> (raw)
Hi,
I'm integrating some code from busybox to mingw tree so that mingw
port can work without msys. Posix utilities such as sed, awk, head,
tail... seem to work well. The main obstacle is ash, which is no where
near usable state (fork issues as always). Busybox ash is about 13000
lines of code, not too big.
Anyone interested in?
--
Duy
next reply other threads:[~2007-07-10 15:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-10 15:32 Nguyen Thai Ngoc Duy [this message]
2007-07-10 15:39 ` [WIP] Get rid of msys in favor of busybox port for windows Johannes Schindelin
2007-07-10 16:08 ` Nguyen Thai Ngoc Duy
2007-07-10 16:20 ` Johannes Schindelin
2007-07-10 16:45 ` Nguyen Thai Ngoc Duy
2007-07-10 15:56 ` Henning Rogge
2007-07-10 16:12 ` Nguyen Thai Ngoc Duy
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=fcaeb9bf0707100832j3c2ff076gab5c9bd4f9d3f4a0@mail.gmail.com \
--to=pclouds@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).