git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Nguyen Thai Ngoc Duy" <pclouds@gmail.com>
To: "Henning Rogge" <hrogge@googlemail.com>
Cc: git@vger.kernel.org
Subject: Re: [WIP] Get rid of msys in favor of busybox port for windows
Date: Tue, 10 Jul 2007 12:12:47 -0400	[thread overview]
Message-ID: <fcaeb9bf0707100912y69d1f406waf094e5f68e36ada@mail.gmail.com> (raw)
In-Reply-To: <87eacd830707100856l3132bee2k45b8d59ac1875d89@mail.gmail.com>

On 7/10/07, Henning Rogge <hrogge@googlemail.com> wrote:
> On 7/10/07, Nguyen Thai Ngoc Duy <pclouds@gmail.com> wrote:
> > 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?
> If I can use it without needing a "vi/vim" implementation I'm interested !

There is no vi/vim in the port :-) My goal is to make shell scripts
work with minimum effort. I don't even attempt to make ash
interactively usable (well, git add --interactive and friends have to
wait longer).
-- 
Duy

      reply	other threads:[~2007-07-10 16:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-10 15:32 [WIP] Get rid of msys in favor of busybox port for windows Nguyen Thai Ngoc Duy
2007-07-10 15:39 ` 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 [this message]

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=fcaeb9bf0707100912y69d1f406waf094e5f68e36ada@mail.gmail.com \
    --to=pclouds@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=hrogge@googlemail.com \
    /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).