git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Aaron Gray <angray@beeb.net>
Cc: Johannes Sixt <J.Sixt@eudaptics.com>, git@vger.kernel.org
Subject: Re: Anyone running GIT on native Windows
Date: Mon, 7 May 2007 16:24:28 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0705071624210.4167@racer.site> (raw)
In-Reply-To: <002801c790ae$d86a1a90$0200a8c0@AMD2500>

Hi,

On Mon, 7 May 2007, Aaron Gray wrote:

> > > On 5/7/07, Johannes Sixt <J.Sixt@eudaptics.com> wrote:
> > > > Aaron Gray wrote:
> > > > > What I want is to be able to work in Windows CMD and envoke .sh 
> > > > > scripts by association (unfortunately you have to add the .sh on 
> > > > > the command name though).
> > > >
> > > > I run the mingw port exclusively from CMD without a .sh 
> > > > association. So exclusively that I don't even know whether any 
> > > > other way of using the tools even works. Of course, you have to 
> > > > get used to
> > > 
> > > Is it public available?
> > 
> > gitweb: http://repo.or.cz/w/git/mingw.git
> > clone:  git://repo.or.cz/git/mingw.git
> > 
> > I only have either time to hack on mingw.git or a Windows 
> > installation, but not both at the same time. Therefore, the port is 
> > now a bit falling back (it's still at 1.5.1). I hope to be able to 
> > change this in a few weeks.
> 
> Great I will check this out when I get some time.
> 
> 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.

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

Ciao,
Dscho

  reply	other threads:[~2007-05-07 14:24 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 [this message]
2007-05-07 15:10               ` Thomas Glanzmann
2007-05-07 16:39               ` Aaron Gray
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=Pine.LNX.4.64.0705071624210.4167@racer.site \
    --to=johannes.schindelin@gmx.de \
    --cc=J.Sixt@eudaptics.com \
    --cc=angray@beeb.net \
    --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).