Re: [msysGit] Re: Release candidate of Git for Windows 2.x is out
On 2015-06-26 13:06, Ties wrote: Do you have an ETA on the final release? No, sorry, no ETA yet. -- To unsubscribe from this list: send the line unsubscribe git in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
3rd release candidate of Git for Windows 2.x, was Re: Release candidate of Git for Windows 2.x is out
Hi all, I just uploaded the 3rd release candidate for the upcoming Git for Windows 2.x release. Please find the download link here: https://git-for-windows.github.io/#download Lots of changes since the first release candidate (v2.4.2, I was too swamped to announce the second release candidate -- v2.4.3 -- I published Friday last week, my apologies). Please find them in the release notes: https://github.com/git-for-windows/build-extra/blob/master/installer/ReleaseNotes.md We're getting closer! Johannes -- To unsubscribe from this list: send the line unsubscribe git in
Re: [msysGit] Re: 3rd release candidate of Git for Windows 2.x, was Re: Release candidate of Git for Windows 2.x is out
Hi Jon, On 2015-06-20 16:59, Jon wrote: On Saturday, June 20, 2015 at 10:16:09 AM UTC-4, Johannes Schindelin wrote: I just uploaded the 3rd release candidate for the upcoming Git for Windows 2.x release. Please find the download link here: https://git-for-windows.github.io/#download Lots of changes since the first release candidate (v2.4.2, I was too swamped to announce the second release candidate -- v2.4.3 -- I published Friday last week, my apologies). Please find them in the release notes: https://github.com/git-for-windows/build-extra/blob/master/installer/ReleaseNotes.md 1) Why are there two ssl/certs trees? (e.g. - one is used by git-bash.exe and the other git-cmd.exe and cmd/git.exe?) Please keep in mind that Git for Windows is a hybrid collection of pure Win32 executables and MSys2 executables (MSys2 is a stripped-down Cygwin providing a POSIX emulation layer on top of the Win32 API[*1*]). They are separated into the `/usr/` and the `/mingw64/` directories, respectively (`/mingw32/` for 32-bit). An example for a pure Win32 executable is `git.exe` while Perl and Bash are MSys2 executables. In general, we avoid MSys2 as much as possible: while it provides a nice POSIX emulation layer, it comes at a noticable performance penalty. So whenever we can get away with using OpenSSL compiled as pure Win32 library, we do so. Cloning via HTTPS falls into that category. When it comes to `git-svn` -- something that is needed by many users, still, and indeed the motivation for the most prolific contributor helping me with Git for Windows 2.x -- it is not that easy, though: `git-svn` is a Perl script, our Perl is an MSys2 program and therefore uses OpenSSL compiled as MSys2 library. That is the reason why we have separate ssl/ directory structures. One for MinGW (i.e. pure Win32) programs and one for MSys2 ones. 2) Why are INSTALL_DIR/usr/ssl/certs/ca-bundle.crt and INSTALL_DIR/mingw64/ssl/certs/ca-bundle.crt different? We simply use the packages provided by MSys2. The MinGW/MSys2 ca-certificates packages are sometimes out of sync, and that is what you are seeing here. Now, theoretically it would be possible to reconcile the different ca-certificates packages into a single one. The correct way to go about this would be by contributing to the MSys2 project: that way, not only Git for Windows but really all MSys2-based projects benefit from it. Ciao, Johannes Footnote *1*: https://msys2.github.io/ -- To unsubscribe from this list: send the line unsubscribe git in
Re: [msysGit] Re: Release candidate of Git for Windows 2.x is out
Hi, On 2015-06-09 14:10, QbProg wrote: I reproduce it using the windows command prompt (cmd.exe) using any repository. I tryed with bash and it works correctly. Please note that you removed enough context that the mail does not make sense anymore if read individually. At this point it might be best to open a ticket, as I suggested in my announcement: just log into GitHub (or sign up for free) and direct your web browser to https://github.com/git-for-windows/git/issues/new. For the record: I tried again, with `Git CMD`, this time I called ```cmd git clone https://github.com/dscho/images.git octo2 ``` ... and octo2/ is created correctly and contains the `.git/` subdirectory (which is hidden by default, but you can call `cd octo2/.git`). Read: I still cannot reproduce the issue. Ciao, Johannes -- To unsubscribe from this list: send the line unsubscribe git in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [msysGit] Re: Release candidate of Git for Windows 2.x is out
Hi, On 2015-06-09 10:43, Qb wrote: I'm trying the release candidate on Win 8.1. Everything's working now, but when I clone a repository git clone http://./name.git CustomFolder it creates CustomFolder with the checkout files, but the .git folder is created inside CustomFolder\CustomFolder\ I cannot reproduce this behavior. This is what I did to test: 1. install Git-2.4.2.1-release-candidate-64.exe (default options) 2. run Git Bash 3. git clone https://github.com/dscho/images.git octocats This results in a correct checkout: `$HOME/octocats/.git/` exists and contains the local repository. Ciao, Johannes -- To unsubscribe from this list: send the line unsubscribe git in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Release candidate of Git for Windows 2.x is out
Hi all, I just uploaded release candidates for the upcoming Git for Windows 2.x release. Please find the download link here: https://git-for-windows.github.io/#download There are 32-bit and 64-bit versions both of regular installers and portable installers (portable meaning that they are .7z archives that can be unpacked anywhere and run in place, without any need for running an installer). My projected time line is to hammer out the last kinks until Friday, and then continue after a one-week leave, if needed, and then finally retire msysGit and start the official 2.x release cycle of Git for Windows. If you are running Windows and have a little time to spare, please test this release candidate thoroughly. If you find bugs, please first look at https://github.com/git-for-windows/git/issues (even the closed ones), and comment either on existing tickets or open new ones. It would be even cooler, of course, if you could open Pull Requests with fixes :-) Ciao, Johannes -- To unsubscribe from this list: send the line unsubscribe git in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html