{"thread":{"id":"36344","subject":"[ANNOUNCE] WinGit - native x86/x64 Git for Windows","startedAt":"2014-04-03T13:18:50Z","lastAt":"2014-04-19T19:24:09Z","messageCount":9,"participants":["marat@slonopotamus.org","Konstantin Khomoutov","Marat Radchenko","Vincent van Ravesteijn","Felipe Contreras","Heiko Voigt","Johannes Schindelin"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"238346","messageId":"20140403131850.GA24449@seldon","threadId":"36344","inReplyTo":null,"subject":"[ANNOUNCE] WinGit - native x86/x64 Git for Windows","fromName":"","fromEmail":"marat@slonopotamus.org","sentAt":"2014-04-03T13:18:50Z","receivedAt":"2014-04-03T13:18:50Z","isPatch":false,"sender":{"key":"marat@slonopotamus.org","avatar":"https://avatars.githubusercontent.com/u/92637?v=4"},"body":"I'm proud to announce WinGit:\nan attempt to bring Git powers to 64-bit Windows.\n\nWinGit is currently used only by my coworkers and isn't considered\nproduction-ready-rock-solid. Use at your own risk.\n\n\nHomepage & build instructions\n-----------------------------\nhttps://github.com/slonopotamus/wingit\n\n\nBinaries\n--------\nMSI packages: https://github.com/slonopotamus/wingit/releases\n\nAfter installation, git.exe is ready to be used from cmd.exe or TortoiseGit.\nNo kind of \"Git Bash\" or own explorer integration is provided.\n\n\nIssues\n------\nOf course WinGit has issues:\nhttps://github.com/slonopotamus/wingit/issues?state=open\n\nMost notable are: git documentation is not packaged, no Tcl/Tk (thus, no gitk),\nno SVN, no Explorer integration.\n\n\nSources\n------------------\n\nAll sources are available on GitHub: https://github.com/slonopotamus/wingit\n\nI know that build.sh is UGLY, especially openssl part.\n\n\nRelationship with msysgit\n=========================\n\nUnlike msysgit, WinGit is a pure-Windows binary build with MSVC.\n\nLike msysgit, WinGit also uses msys environment (sh/perl/etc) both during\nbuild-time and runtime.\n\nWinGit adds a few patches to Git itself on top of msysgit ones.\nPatches are required due to insufficient testing of MSVC builds\n(caused by total absence of any MSVC-built Git distributions).\n\nAll WinGit patches are sent upstream, just didn't get to master yet.\n"},{"id":"238349","messageId":"20140403174808.9ae91c3bd477d276e3e80d68@domain007.com","threadId":"36344","inReplyTo":"20140403131850.GA24449@seldon","subject":"Re: [ANNOUNCE] WinGit - native x86/x64 Git for Windows","fromName":"Konstantin Khomoutov","fromEmail":"flatworm@users.sourceforge.net","sentAt":"2014-04-03T13:48:08Z","receivedAt":"2014-04-03T13:48:08Z","isPatch":false,"sender":{"key":"flatworm@users.sourceforge.net","avatar":null},"body":"On Thu, 3 Apr 2014 17:18:50 +0400\nmarat@slonopotamus.org wrote:\n\n> I'm proud to announce WinGit:\n> an attempt to bring Git powers to 64-bit Windows.\n[...]\n> Relationship with msysgit\n> =========================\n> \n> Unlike msysgit, WinGit is a pure-Windows binary build with MSVC.\n> \n> Like msysgit, WinGit also uses msys environment (sh/perl/etc) both\n> during build-time and runtime.\n> \n> WinGit adds a few patches to Git itself on top of msysgit ones.\n> Patches are required due to insufficient testing of MSVC builds\n> (caused by total absence of any MSVC-built Git distributions).\n> \n> All WinGit patches are sent upstream, just didn't get to master yet.\n\nWhat is the state of Unicode support in WinGit?\n"},{"id":"238350","messageId":"20140403140701.GA24817@seldon","threadId":"36344","inReplyTo":"20140403174808.9ae91c3bd477d276e3e80d68@domain007.com","subject":"Re: [ANNOUNCE] WinGit - native x86/x64 Git for Windows","fromName":"Marat Radchenko","fromEmail":"marat@slonopotamus.org","sentAt":"2014-04-03T14:07:02Z","receivedAt":"2014-04-03T14:07:02Z","isPatch":false,"sender":{"key":"marat@slonopotamus.org","avatar":"https://avatars.githubusercontent.com/u/92637?v=4"},"body":"On Thursday 03 April 2014 at 17:48:08  Konstantin Khomoutov wrote:\n>\n> What is the state of Unicode support in WinGit?\n\nI haven't seen any Unicode-related issues when using through TortoiseGit.\n\nCommand-line usage is currently broken: no UTF-8 <->cmd.exe encoding\nconversion is performed. Fixing this is a high-priority issue though,\nmost likely by migrating to newer (yet-to-be-released) msys lib.\n"},{"id":"238351","messageId":"CAAH6HY_QkDdf9Leh2dZ-T_8UZa68xDL5e3N1go1Lgs-3fJZHmw@mail.gmail.com","threadId":"36344","inReplyTo":"CAAH6HY8DbQCMJhb4fY3-aLbriUHOS4zeizHjPy+FMmxuyHQxxQ@mail.gmail.com","subject":"Fwd: [ANNOUNCE] WinGit - native x86/x64 Git for Windows","fromName":"Vincent van Ravesteijn","fromEmail":"vfr@lyx.org","sentAt":"2014-04-03T15:03:14Z","receivedAt":"2014-04-03T15:03:14Z","isPatch":false,"sender":{"key":"vfr@lyx.org","avatar":"https://avatars.githubusercontent.com/u/687868?v=4"},"body":">\n> I know that build.sh is UGLY, especially openssl part.\n>\n> Unlike msysgit, WinGit is a pure-Windows binary build with MSVC.\n>\n> Like msysgit, WinGit also uses msys environment (sh/perl/etc) both during\n> build-time and runtime.\n>\n> WinGit adds a few patches to Git itself on top of msysgit ones.\n> Patches are required due to insufficient testing of MSVC builds\n> (caused by total absence of any MSVC-built Git distributions).\n>\n\n\nI've created CMake files to be able to build git with MSVC without the\nneed for msys. I haven't tested it with latest git and didn't really\nsee the recent changes with respect to compilation with MSVC.\n\nBut, if you're interested, let me know.\n\nVincent\n"},{"id":"238588","messageId":"534583107c84_af197d308d9@nysa.notmuch","threadId":"36344","inReplyTo":"20140403131850.GA24449@seldon","subject":"RE: [ANNOUNCE] WinGit - native x86/x64 Git for Windows","fromName":"Felipe Contreras","fromEmail":"felipe.contreras@gmail.com","sentAt":"2014-04-09T17:27:44Z","receivedAt":"2014-04-09T17:27:44Z","isPatch":false,"sender":{"key":"felipe.contreras@gmail.com","avatar":"https://avatars.githubusercontent.com/u/8358?v=4"},"body":"marat@ wrote:\n> I'm proud to announce WinGit: an attempt to bring Git powers to 64-bit\n> Windows.\n> \n> WinGit is currently used only by my coworkers and isn't considered\n> production-ready-rock-solid. Use at your own risk.\n\nThank you for doing this, it's very much needed. It would be great if there was\na place to list all the tools that need to be converted to C, so that neither\nPerl, nor a shell are needed for most of Git's operations, don't you think?\n\nCheers.\n\n-- \nFelipe Contreras\n"},{"id":"239097","messageId":"20140419063133.GA3617@book-mint","threadId":"36344","inReplyTo":"20140403131850.GA24449@seldon","subject":"Re: [ANNOUNCE] WinGit - native x86/x64 Git for Windows","fromName":"Heiko Voigt","fromEmail":"hvoigt@hvoigt.net","sentAt":"2014-04-19T06:31:34Z","receivedAt":"2014-04-19T06:31:34Z","isPatch":false,"sender":{"key":"hvoigt@hvoigt.net","avatar":"https://avatars.githubusercontent.com/u/184958?v=4"},"body":"Hi Marat,\n\nOn Thu, Apr 03, 2014 at 05:18:50PM +0400, marat@slonopotamus.org wrote:\n> I'm proud to announce WinGit:\n> an attempt to bring Git powers to 64-bit Windows.\n\nSo the reason for this new package is that you need 64bit binaries?\n\n> Relationship with msysgit\n> =========================\n> \n> Unlike msysgit, WinGit is a pure-Windows binary build with MSVC.\n> \n> Like msysgit, WinGit also uses msys environment (sh/perl/etc) both during\n> build-time and runtime.\n\nI can see the need for a pure Windows solution (no msys tools at least for\nruntime). But this sounds to me that the only thing you changed is the\ncompiler and 64bit? The git binaries in msysgit are already pure Windows\nbinaries with no need of msys.dll. The only reason why so many other\ntools are shipped with msysgit is to run scripted commands (e.g. like\ngitk or rebase).\n\nWhat is the reason of using a closed source compiler? Why not use the\n64bit mingw that is already used to build the 64bit explorer extension\nto package 64bit binaries along with the 32bit ones in the installer?\n\nSorry if I am a little bit skeptic, but I am wondering whether it does\nmake sense for you to join forces with msysgit instead of creating a\nfork? I think the main reason why there are no 64 bit binaries shipped\nwith msysgit is that nobody needed them and the need to ship both (at\nleast for some time).\n\nThat would also make the maintenance burden easier for you.\n\nCheers Heiko\n\n-- \n-- \n*** Please reply-to-all at all times ***\n*** (do not pretend to know who is subscribed and who is not) ***\n*** Please avoid top-posting. ***\nThe msysGit Wiki is here: https://github.com/msysgit/msysgit/wiki - Github accounts are free.\n\nYou received this message because you are subscribed to the Google\nGroups \"msysGit\" group.\nTo post to this group, send email to msysgit@googlegroups.com\nTo unsubscribe from this group, send email to\nmsysgit+unsubscribe@googlegroups.com\nFor more options, and view previous threads, visit this group at\nhttp://groups.google.com/group/msysgit?hl=en_US?hl=en\n\n--- \nYou received this message because you are subscribed to the Google Groups \"msysGit\" group.\nTo unsubscribe from this group and stop receiving emails from it, send an email to msysgit+unsubscribe@googlegroups.com.\nFor more options, visit https://groups.google.com/d/optout.\n"},{"id":"239114","messageId":"alpine.DEB.1.00.1404191719280.14982@s15462909.onlinehome-server.info","threadId":"36344","inReplyTo":"20140419063133.GA3617@book-mint","subject":"Re: Re: [ANNOUNCE] WinGit - native x86/x64 Git for Windows","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2014-04-19T15:24:33Z","receivedAt":"2014-04-19T15:24:33Z","isPatch":false,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi,\n\nOn Sat, 19 Apr 2014, Heiko Voigt wrote:\n\n> On Thu, Apr 03, 2014 at 05:18:50PM +0400, marat@slonopotamus.org wrote:\n> > I'm proud to announce WinGit:\n> > an attempt to bring Git powers to 64-bit Windows.\n> \n> So the reason for this new package is that you need 64bit binaries?\n> \n> > Relationship with msysgit\n> > =========================\n> > \n> > Unlike msysgit, WinGit is a pure-Windows binary build with MSVC.\n\nMarat, please do not add to the confusion. \"msysGit\" is the name of the\n*development environment* for developing Git for Windows. It also brings\nfacilities to use MSVC instead of GCC.\n\nSo do not compare WinGit to msysgit (that would be like comparing Git to\nGCC). Compare WinGit to Git for Windows (and clarify that you mean a\ndifferent WinGit than the old name of Git for Windows).\n\n> > Like msysgit, WinGit also uses msys environment (sh/perl/etc) both\n> > during build-time and runtime.\n\nSo it is not purely 64-bit, because MSys is not.\n\n> I can see the need for a pure Windows solution (no msys tools at least for\n> runtime). But this sounds to me that the only thing you changed is the\n> compiler and 64bit? The git binaries in msysgit are already pure Windows\n> binaries with no need of msys.dll. The only reason why so many other\n> tools are shipped with msysgit is to run scripted commands (e.g. like\n> gitk or rebase).\n> \n> What is the reason of using a closed source compiler? Why not use the\n> 64bit mingw that is already used to build the 64bit explorer extension\n> to package 64bit binaries along with the 32bit ones in the installer?\n> \n> Sorry if I am a little bit skeptic, but I am wondering whether it does\n> make sense for you to join forces with msysgit instead of creating a\n> fork? I think the main reason why there are no 64 bit binaries shipped\n> with msysgit is that nobody needed them and the need to ship both (at\n> least for some time).\n\nWe do have a facility to build 64-bit binaries with msysGit. It is even\ndirt-easy: just run the two release scripts in /src/mingw-w64/, and then\nbuild Git with \"make W64=1\".\n\nThe real reason why Git for Windows does not ship 64-bit binaries is that\nthey did not pass the test suite last time I tried.\n\nAnd for the record: I would have welcome contributions to the Git for\nWindows project. I still will. After all, there is no reason for yet\nanother fork.\n\nCiao,\nJohannes\n\n-- \n-- \n*** Please reply-to-all at all times ***\n*** (do not pretend to know who is subscribed and who is not) ***\n*** Please avoid top-posting. ***\nThe msysGit Wiki is here: https://github.com/msysgit/msysgit/wiki - Github accounts are free.\n\nYou received this message because you are subscribed to the Google\nGroups \"msysGit\" group.\nTo post to this group, send email to msysgit@googlegroups.com\nTo unsubscribe from this group, send email to\nmsysgit+unsubscribe@googlegroups.com\nFor more options, and view previous threads, visit this group at\nhttp://groups.google.com/group/msysgit?hl=en_US?hl=en\n\n--- \nYou received this message because you are subscribed to the Google Groups \"msysGit\" group.\nTo unsubscribe from this group and stop receiving emails from it, send an email to msysgit+unsubscribe@googlegroups.com.\nFor more options, visit https://groups.google.com/d/optout.\n"},{"id":"239115","messageId":"20140419165832.GA23227@seldon","threadId":"36344","inReplyTo":"alpine.DEB.1.00.1404191719280.14982@s15462909.onlinehome-server.info","subject":"Re: Re: [ANNOUNCE] WinGit - native x86/x64 Git for Windows","fromName":"Marat Radchenko","fromEmail":"marat@slonopotamus.org","sentAt":"2014-04-19T16:58:32Z","receivedAt":"2014-04-19T16:58:32Z","isPatch":false,"sender":{"key":"marat@slonopotamus.org","avatar":"https://avatars.githubusercontent.com/u/92637?v=4"},"body":"On Sat, Apr 19, 2014 at 05:24:33PM +0200, Johannes Schindelin wrote:\n> Marat, please do not add to the confusion. \"msysGit\" is the name of the\n> *development environment* for developing Git for Windows.\n\nThis confusion comes from the fact that major part of msysGit is packaged\nwith Git for Windows to be used at runtime.\n\nIf you insist on msysGit-is-a-development-environment, you have to admit\nthat msysGit is technically a fork of msys.\n\nMy approach undoes this fork step and uses upstream runtime environment\nas-is, be it msys, msys2, Cygwin or even SUA [1]. I could even make it a\nnoop and say \"dear user, I don't care how, but please put sh/awk/find/etc\non PATH to make Git work, like things normally happen in *nix world\".\n\nActually, even if Git was pure C, things like `git filter-branch` would\nbe almost useless without coreutils & friends.\n\n> After all, there is no reason for yet another fork.\n\nIf there wasn't, mingwGitDevEnv would not be started.\n\nI'd say I am doing a 'rebase' instead of 'fork' by using codebase of\nGit for Windows (upstream Git sources with Windows-specific patches)\nbut replacing msysGit-provided runtime environment with another one.\n\n[1]: http://en.wikipedia.org/wiki/Windows_Services_for_UNIX\n\n-- \n-- \n*** Please reply-to-all at all times ***\n*** (do not pretend to know who is subscribed and who is not) ***\n*** Please avoid top-posting. ***\nThe msysGit Wiki is here: https://github.com/msysgit/msysgit/wiki - Github accounts are free.\n\nYou received this message because you are subscribed to the Google\nGroups \"msysGit\" group.\nTo post to this group, send email to msysgit@googlegroups.com\nTo unsubscribe from this group, send email to\nmsysgit+unsubscribe@googlegroups.com\nFor more options, and view previous threads, visit this group at\nhttp://groups.google.com/group/msysgit?hl=en_US?hl=en\n\n--- \nYou received this message because you are subscribed to the Google Groups \"msysGit\" group.\nTo unsubscribe from this group and stop receiving emails from it, send an email to msysgit+unsubscribe@googlegroups.com.\nFor more options, visit https://groups.google.com/d/optout.\n"},{"id":"239135","messageId":"20140419192409.GA8140@book-mint","threadId":"36344","inReplyTo":"20140419165832.GA23227@seldon","subject":"Re: Re: Re: [ANNOUNCE] WinGit - native x86/x64 Git for Windows","fromName":"Heiko Voigt","fromEmail":"hvoigt@hvoigt.net","sentAt":"2014-04-19T19:24:09Z","receivedAt":"2014-04-19T19:24:09Z","isPatch":false,"sender":{"key":"hvoigt@hvoigt.net","avatar":"https://avatars.githubusercontent.com/u/184958?v=4"},"body":"On Sat, Apr 19, 2014 at 08:58:32PM +0400, Marat Radchenko wrote:\n> On Sat, Apr 19, 2014 at 05:24:33PM +0200, Johannes Schindelin wrote:\n> > Marat, please do not add to the confusion. \"msysGit\" is the name of the\n> > *development environment* for developing Git for Windows.\n> \n> This confusion comes from the fact that major part of msysGit is packaged\n> with Git for Windows to be used at runtime.\n\nOnly the tools that are needed to run git (and some that the\ncontributors like) are packaged in Git for Windows. For example there is\nno compiler or similar packaged.\n\n> If you insist on msysGit-is-a-development-environment, you have to admit\n> that msysGit is technically a fork of msys.\n\nWell it is a git repository that conveniently packages all the needed\ntools you need to build \"Git for Windows\" together. It is a little bit\nquick and dirty but it works. We have nothing against improving this\nsituation.\n\n> My approach undoes this fork step and uses upstream runtime environment\n> as-is, be it msys, msys2, Cygwin or even SUA [1]. I could even make it a\n> noop and say \"dear user, I don't care how, but please put sh/awk/find/etc\n> on PATH to make Git work, like things normally happen in *nix world\".\n> \n> Actually, even if Git was pure C, things like `git filter-branch` would\n> be almost useless without coreutils & friends.\n> \n> > After all, there is no reason for yet another fork.\n> \n> If there wasn't, mingwGitDevEnv would not be started.\n\nI would not consider mingwGitDevEnv a fork. It is more msysgit next\ngeneration. But it needs more work to fully replace msysgit.\n\n> I'd say I am doing a 'rebase' instead of 'fork' by using codebase of\n> Git for Windows (upstream Git sources with Windows-specific patches)\n> but replacing msysGit-provided runtime environment with another one.\n\nThe downside of doing this approach is that you regularly have to update\nyour 'rebase' and fix problems. If you integrate your changes into\nmsysgit itself you do not have to do that anymore.\nWell, if it is one of your changes that breaks something, it still would\nbe nice if you do so ;-)\n\n> [1]: http://en.wikipedia.org/wiki/Windows_Services_for_UNIX\n\nCheers Heiko\n\nP.S.: BTW, just in case: Being criticized in open-source is good. Even\nthough it might not feel like that. It means people care about the stuff\nyou do and think it is important enough it deserves a reply. They just\nwant to help you improve it.\n\n-- \n-- \n*** Please reply-to-all at all times ***\n*** (do not pretend to know who is subscribed and who is not) ***\n*** Please avoid top-posting. ***\nThe msysGit Wiki is here: https://github.com/msysgit/msysgit/wiki - Github accounts are free.\n\nYou received this message because you are subscribed to the Google\nGroups \"msysGit\" group.\nTo post to this group, send email to msysgit@googlegroups.com\nTo unsubscribe from this group, send email to\nmsysgit+unsubscribe@googlegroups.com\nFor more options, and view previous threads, visit this group at\nhttp://groups.google.com/group/msysgit?hl=en_US?hl=en\n\n--- \nYou received this message because you are subscribed to the Google Groups \"msysGit\" group.\nTo unsubscribe from this group and stop receiving emails from it, send an email to msysgit+unsubscribe@googlegroups.com.\nFor more options, visit https://groups.google.com/d/optout.\n"}]}