From: Johannes Sixt <J.Sixt@eudaptics.com>
To: hanwen@xs4all.nl
Cc: Marco Costalba <mcostalba@gmail.com>, git@vger.kernel.org
Subject: Re: Anyone running GIT on native Windows
Date: Fri, 11 May 2007 18:34:21 +0200 [thread overview]
Message-ID: <46449B0D.5FCD66F1@eudaptics.com> (raw)
In-Reply-To: 4643EA77.4040803@xs4all.nl
Han-Wen Nienhuys wrote:
> http://lilypond.org/git/binaries/mingw/git-1.5.1-1.mingw.exe
This resulted in a mostly working git toolset after I've done this in
addition to installing it:
- Installed MSYS (of course ;)
- Install libiconv-2.dll, which can be found in
diffutils-2.8.7-1-dep.zip from
http://sourceforge.net/project/showfiles.php?group_id=2435 (available in
Section Snapshot->MSYS) (rename libiconv2.dll to libiconv-2.dll)
- Set the path to MSYS and Git manually.
For extra bonus points, I should also have installed
bash-3.1-MSYS-1.0.11-snapshot.tar.bz2 (without which 'git am' fails) and
msysDTK-1.0.1.exe for ssh and perl, but I haven't.
gitk and git-gui are untested; they need tcltk-8.4.1-1.exe, of course.
-- Hannes
next prev parent reply other threads:[~2007-05-11 16:34 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
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 [this message]
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=46449B0D.5FCD66F1@eudaptics.com \
--to=j.sixt@eudaptics.com \
--cc=git@vger.kernel.org \
--cc=hanwen@xs4all.nl \
--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 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.