Re: Switching from CVS to GIT

From: Steffen Prohaska <prohaska@zib.de>
Date: Oct 15, 2007, 07:56 UTC
Message-ID: <AD60F584-7AAD-4083-9BA6-21F0D00D6D1D@zib.de>
In-Reply-To: <E1IhJ4K-00086x-5U@fencepost.gnu.org>

On Oct 15, 2007, at 8:04 AM, Eli Zaretskii wrote:

Show 21 quoted lines

>> Date: Mon, 15 Oct 2007 02:24:53 +0100 (BST)
>> From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
>> cc: Eli Zaretskii <eliz@gnu.org>, Alex Riesen  
>> <raa.lkml@gmail.com>, ae@op5.se,
>>     tsuna@lrde.epita.fr, make-w32@gnu.org
>>
>> To clarify: git works on Windows.  Most of the time, that is.  But  
>> all
>> those changes that were necessary to go there have not yet found  
>> their way
>> into the official git.git repository.
>
> I, for one, appreciate all the hard work invested in that.
>
> While we are at that: can you (or someone else) point me to
> instructions on how to build the MinGW port of GIT?  I found a tarball
> of the MinGW-ported GIT (v1.5.3, I think), but what I don't seem to be
> able to find is some kind of HOWTO: what tools I need to have
> installed, how to configure them (if there are any special issues
> there), what command(s) to type, etc.  Is there anything like that out
> there, or can someone post such instructions?

If you want to have a full working development environment, such that you can start contributing to msysgit right away, and have no firewall issues, go to

	http://code.google.com/p/msysgit/

and install GitMe, currently

	http://msysgit.googlecode.com/files/GitMe-0.4.2.exe

If you only care about an end-user setup, which contains only the git binaries on your system, but no tools to compile them, stay tuned for one or two days. We'll release an updated installer soon.

	Steffen