All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Aaron Gray" <angray@beeb.net>
To: "Johannes Schindelin" <Johannes.Schindelin@gmx.de>
Cc: "Johannes Sixt" <J.Sixt@eudaptics.com>, <git@vger.kernel.org>
Subject: Re: Anyone running GIT on native Windows
Date: Mon, 7 May 2007 17:39:42 +0100	[thread overview]
Message-ID: <00c701c790c6$512804d0$0200a8c0@AMD2500> (raw)
In-Reply-To: Pine.LNX.4.64.0705071624210.4167@racer.site

Hi,

>> An .sh to c converter would be the best solution. I will be looking into
>> how hard this would be to do.
>
> NACK.
>
> A stupid .sh to c converter will almost certainly result in slow and
> hard-to-debug code.

I had presumed you do not have to really look at the code if the tanslator 
is sound.

> If you had bothered to check, you'd know that there are ongoing efforts to
> do the ports properly.

This is good. So the shell code is being migrated to C ?

Could you give me a link or refernce please ?

Aaron

  parent reply	other threads:[~2007-05-07 16:47 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-06  6:50 Anyone running GIT on native Windows Aaron Gray
2007-05-06  7:19 ` Junio C Hamano
2007-05-06  7:39   ` Aaron Gray
2007-05-07  7:02     ` Johannes Sixt
2007-05-07 11:48       ` Marco Costalba
2007-05-07 12:01         ` Johannes Sixt
2007-05-07 12:38           ` A.S. Bradbury
2007-05-07 13:51           ` Aaron Gray
2007-05-07 14:24             ` Johannes Schindelin
2007-05-07 15:10               ` Thomas Glanzmann
2007-05-07 16:39               ` Aaron Gray [this message]
2007-05-07 17:45                 ` Johannes Schindelin
2007-05-08 18:21           ` Asger Ottar Alstrup
2007-05-09  4:41           ` Han-Wen Nienhuys
2007-05-09  7:08             ` Johannes Sixt
2007-05-11  4:00               ` Han-Wen Nienhuys
2007-05-11 16:34                 ` Johannes Sixt
2007-05-11 17:35                   ` Han-Wen Nienhuys
2007-05-11 20:07                     ` Johannes Sixt
2007-05-11 22:08                       ` Han-Wen Nienhuys
2007-05-12  2:23                   ` Aaron Gray
2007-05-09 18:31             ` Jan Hudec
2007-05-09 18:40               ` Han-Wen Nienhuys

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='00c701c790c6$512804d0$0200a8c0@AMD2500' \
    --to=angray@beeb.net \
    --cc=J.Sixt@eudaptics.com \
    --cc=Johannes.Schindelin@gmx.de \
    --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.