git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Nguyen Thai Ngoc Duy <pclouds@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: [WIP] Get rid of msys in favor of busybox port for windows
Date: Tue, 10 Jul 2007 17:20:48 +0100 (BST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0707101719390.4047@racer.site> (raw)
In-Reply-To: <fcaeb9bf0707100908o4be761b9t920cdc65a72d9aee@mail.gmail.com>

Hi,

On Tue, 10 Jul 2007, Nguyen Thai Ngoc Duy wrote:

> On 7/10/07, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
> > 
> > On Tue, 10 Jul 2007, Nguyen Thai Ngoc Duy 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?
> > 
> > Definitely.
> > 
> > Last time I wanted to assess how much work it is to compile that on MinGW,
> > though, it seemed to be too much to be tractable.
> 
> The exact answer is "I don't know" :-) I cross compile all the time
> however it should build fine on MinGW as it now uses git Makefile.
> I'll push the patch into mob soon.

Do you mean the whole busybox thing?

If so, please do not put it into mingw.git.  Rather, start a busybox.git 
project (I saw that you have already some projects on repo.or.cz, so it 
should be easy for you.)

Thanks,
Dscho

  reply	other threads:[~2007-07-10 16:28 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 [this message]
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=Pine.LNX.4.64.0707101719390.4047@racer.site \
    --to=johannes.schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=pclouds@gmail.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).