On 5/7/07, Johannes Sixt <J.Sixt@xxxxxxxxxxxxx> 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 - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html