From: Johannes Sixt <J.Sixt@eudaptics.com>
To: git@vger.kernel.org
Subject: Re: Anyone running GIT on native Windows
Date: Mon, 07 May 2007 09:02:12 +0200 [thread overview]
Message-ID: <463ECEF4.625F3633@eudaptics.com> (raw)
In-Reply-To: 2b7f01c78fb1$be4dc6a0$0200a8c0@AMD2500
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
git status
git fetch
git commit
git rebase
etc. instead of
git-status
git-fetch
git-commit
git-rebase
and I also use CMD's tab completion frequently, with leaves \ instead of
/ in the paths. I also quite often do
git clone p:\public\repos\foo.git
and
git clone p:/public/repos/foo.git
without a hitch.
Sure, you need a set of Posix tools (sed, grep, cat, wc, sort, ...)
including a Bourne shell that knows how to invoke other scripts by
parsing the interpreter from the first line (#!/bin/sh). (But the perl
scripts (git-remote) will probably work only with MinGW's perl.)
-- Hannes
next prev parent reply other threads:[~2007-05-07 7:02 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 [this message]
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
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=463ECEF4.625F3633@eudaptics.com \
--to=j.sixt@eudaptics.com \
--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.