git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Sixt <J.Sixt@eudaptics.com>
To: Marco Costalba <mcostalba@gmail.com>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>, git@vger.kernel.org
Subject: Re: MinGW port (was: Re: [ANNOUNCE] qgit4 aka qgit ported to Windows)
Date: Thu, 11 Jan 2007 14:24:39 +0100	[thread overview]
Message-ID: <45A63A97.E160751F@eudaptics.com> (raw)
In-Reply-To: e5bfff550701110456y51b8b678s59974cc1d8655a90@mail.gmail.com

Marco Costalba wrote:
> > On Thu, 11 Jan 2007, Johannes Sixt wrote:
> > > [*] because shell scripts like merge-one-file can't be invoked from an
> > > exe like merge-index, yet. Fortunately this looks like the easiest part
> > > to solve.
> >
> 
> >From an exe you could run:
> 
>      cmd.exe /c  <script with arguments>
> 
> Of course the problem is that the content of the script should be
> understandable by cmd.exe windows interpreter.

We are talking about git's own scripts, which are (ba)sh and perl.

The route I'm going is to do the path lookup manually (if necessary),
then look at the first few bytes of the file for the interpreter, then
something like

 spawnvp(<interpreter-w/o-path>, <full-path-of-script plus args>)

-- Hannes

  reply	other threads:[~2007-01-11 13:50 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-09 21:14 [ANNOUNCE] qgit4 aka qgit ported to Windows Marco Costalba
2007-01-09 21:55 ` Josef Weidendorfer
2007-01-09 22:30   ` Marco Costalba
2007-01-09 22:47     ` Yann Dirson
2007-01-10 23:17 ` Martin Langhoff
2007-01-11  8:47   ` Johannes Schindelin
2007-01-11  9:35   ` MinGW port (was: Re: [ANNOUNCE] qgit4 aka qgit ported to Windows) Johannes Sixt
2007-01-11  9:39     ` Johannes Schindelin
2007-01-11 12:56       ` Marco Costalba
2007-01-11 13:24         ` Johannes Sixt [this message]
2007-01-11 12:19   ` [ANNOUNCE] qgit4 aka qgit ported to Windows Marco Costalba
2007-01-11 12:27     ` Andreas Ericsson
2007-01-11 12:49       ` Marco Costalba

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=45A63A97.E160751F@eudaptics.com \
    --to=j.sixt@eudaptics.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=mcostalba@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).