From: "Marco Costalba" <mcostalba@gmail.com>
To: "Johannes Sixt" <J.Sixt@eudaptics.com>
Cc: git@vger.kernel.org
Subject: Re: Anyone running GIT on native Windows
Date: Mon, 7 May 2007 13:48:08 +0200 [thread overview]
Message-ID: <e5bfff550705070448t7813d064mbac82abb45591888@mail.gmail.com> (raw)
In-Reply-To: <463ECEF4.625F3633@eudaptics.com>
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?
I see this as the long term solution to bring git under Windows
(Cygwin is just a temporary shortcut although very useful).
Why to port git under Windows?
Simply, to have better possibility to be chosen by the big projects under Linux!
See Mozilla-Firefox, as example, but not only, some of the biggest
projects under Linux are already ported or are being ported under
Windows (Apache, MySQL, OpenOffice, etc..) and in the future KDE.
Adopting a SCM that has a native porting under Windows is more and
more a sensible choice for the Linux big players.
The problem is that you don't chose an SCM each week, so when the
choice is made you have to wait years to have another opportunity (see
again Mozilla-Firefox thread on this subject), so not only git native
on Windows is the way to go, but also possibly quickly.
Marco
next prev parent reply other threads:[~2007-05-07 11:48 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 [this message]
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=e5bfff550705070448t7813d064mbac82abb45591888@mail.gmail.com \
--to=mcostalba@gmail.com \
--cc=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 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).