[ANNOUNCE] Git for Windows 2.27.0-rc0

[Johannes Schindelin]

Dear Git users,

I hereby announce that Git for Windows 2.27.0-rc0 is available from:

https://github.com/git-for-windows/git/releases/tag/v2.27.0-rc0.windows.1

Changes since Git for Windows v2.26.2 (April 20th 2020)

New Features

* Comes with Git v2.27.0-rc0.
* Comes with OpenSSL v1.1.1g.
* Comes with perl-YAML-Syck v1.32.
* Comes with perl-HTML-Parser v3.72.
* Comes with cURL v7.70.0.
* Comes with subversion v1.13.0.
* Comes with MSYS2 runtime (Git for Windows flavor) based on Cygwin
3.1.4.
* The release notes have been made a bit more readable and are now
linked from the Start Menu group.
* The Frequently Asked Questions (FAQ) are now linked in a Start Menu
item.
* Comes with perl-Locale-Gettext v1.07.
* Comes with Git LFS v2.11.0.

Bug Fixes

* Some Perl packages (e.g. Net::SSLeay) that had been broken recently
have been fixed.

Git-2.27.0-rc0-64-bit.exe | 14ce81a30c383caab6e31387a4aac1b4b738b63ae33461aac1858f9b878cf530
Git-2.27.0-rc0-32-bit.exe | f38d76a6dc241c3a1d06c15dac79773eee1dcbf9d19bed3ab3fba18c5a08e58d
PortableGit-2.27.0-rc0-64-bit.7z.exe | 90536da1847926b91017736753661c52f01e23842f8fca2a06a4fafeeddac22a
PortableGit-2.27.0-rc0-32-bit.7z.exe | 91a47f140e23e511bb89971760de6a2510ce399177873352e31efcc972abc0d5
MinGit-2.27.0-rc0-64-bit.zip | 5b3e9447c3ec2dce971b3f4ce02f1f06fe4f2097a753e2282306a885a16f3373
MinGit-2.27.0-rc0-32-bit.zip | 631603b87409e735f0e3fde53d46a53d4f191ba40045a049b9f6363a692ca18e
MinGit-2.27.0-rc0-busybox-64-bit.zip | cfe168171ece1b0f8b3df04be3a6e955943d9be0ef9b6f75f042710cf379b642
MinGit-2.27.0-rc0-busybox-32-bit.zip | 1de6b0896fb813ff2f921e34a84d9b44e0ba9b44ee68fad85de09c415d834b24
Git-2.27.0-rc0-64-bit.tar.bz2 | d62ab1326de35486ad78ac9b85c8af448bbb3745f0388820e87534ead48b6869
Git-2.27.0-rc0-32-bit.tar.bz2 | 3e0b27f0f46b59b052fe02c0b0e4ca0cd01586e82ef30da093844b2aae53d4a0

Ciao,
Johannes

[Bryan Turner]

On Fri, May 15, 2020 at 10:32 AM Johannes Schindelin
<johannes....@gmx.de> wrote:
>
> Dear Git users,
>
> I hereby announce that Git for Windows 2.27.0-rc0 is available from:
>
> https://github.com/git-for-windows/git/releases/tag/v2.27.0-rc0.windows.1

I've added the 2.27.0-rc0 release candidates for Git and Git for
Windows to Bitbucket Server's test matrix. No failures to report.

Thanks as always for these early release candidates!

Best regards,
Bryan Turner

[Johannes Schindelin]

Hi Bryan,

Thank you so much!

To be honest, this time round I would _really_ like to ask for some manual
testing. I upgraded the MSYS2 runtime from being based on Cygwin v3.0.7 to
v3.1.4, and the biggest new feature is support for those new-fangled
pseudo terminals that Windows 10 now supports. I did find a couple of
rough edges in my use cases, but I am not exactly a typical Git for
Windows user...

Could I ask for some manual testing in particular of anything run inside
the Git Bash?

Thanks,
Dscho

[Bryan Turner]

I’m happy to set it up and use it as my daily driver on one of my workstations, but I don’t want to overpromise how much help I can really offer for that sort of testing. I don’t do much of my full-time development on Windows anymore for a variety of reasons, so even if I install it in my Windows machines I won’t get that much active use in. And when I do use Windows, I keep my workflow pretty simple, so aside from basic adds and commits with an occasional checkout or very rare rebase, I just don’t cover that much functionality.

Sorry I can’t offer much when it comes to end user style testing, Dscho.

Thanks,
Dscho

[Mark Waite]

I've installed 2.27.0-rc on my full-time Windows computer and have deployed it into the Jenkins cluster that I use to test the Jenkins git client plugin and Jenkins git plugin.  No issues detected to date.

Thanks for your excellent work, Johannes!

--
You received this message because you are subscribed to the Google Groups "git-for-windows" group.
To unsubscribe from this group and stop receiving emails from it, send an email to git-for-windo...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/git-for-windows/CAGyf7-Fkn2uHLCqM-4qfM0YQAXoMgiMwKEaxkGkOtz%3DpYYKQWg%40mail.gmail.com.

[Johannes Schindelin]

Hi Bryan,

Oh, please don't apologize. I appreciate all your help!

Ciao,
Dscho

[Johannes Schindelin]

Hi Mark,

On Sun, 17 May 2020, Mark Waite wrote:

> I've installed 2.27.0-rc on my full-time Windows computer and have deployed
> it into the Jenkins cluster that I use to test the Jenkins git client
> plugin and Jenkins git plugin. No issues detected to date.

Wonderful!

Thank you for testing,
Dscho

[Johannes Schindelin]

Hi,

Turns out that I ran into even more issues when trying to do a visual
selection in `vim`: it would frequently "lose" the selection when I moved
via the cursor keys.

So I've come to the conclusion that the pseudo console support code is
still too buggy to unleash onto Git for Windows' users, except as an
experimental option. I will patch it to make the pseudo console feature
opt-in instead of opt-out, and then also offer to configure it in Git for
Windows' installer via an experimental option.

Has anybody else run into issues with console programs (such as `vim`,
interactive Bash, etc)? Or is there anybody with a very different
experience than mine, i.e. _not_ having run into any issues despite using
(interactively) Git Bash extensively?

Ciao,
Dscho

[Matthew Kraai]

Hi,

On Tuesday, May 19, 2020 at 4:16:44 AM UTC-7, Johannes Schindelin wrote:

Turns out that I ran into even more issues when trying to do a visual
selection in `vim`: it would frequently "lose" the selection when I moved
via the cursor keys.

So I've come to the conclusion that the pseudo console support code is
still too buggy to unleash onto Git for Windows' users, except as an
experimental option. I will patch it to make the pseudo console feature
opt-in instead of opt-out, and then also offer to configure it in Git for
Windows' installer via an experimental option.

Has anybody else run into issues with console programs (such as `vim`,
interactive Bash, etc)? Or is there anybody with a very different
experience than mine, i.e. _not_ having run into any issues despite using
(interactively) Git Bash extensively?

I've run into the following problems using Git Bash:

* When I run a command that uses the pager, such as `git log`, any keys that I press using the pager appear on the command line after I exit the pager (e.g., if I press G to go to the end of the output and then q to exit the pager, when the prompt is displayed it displays "Gq", which I have to delete before entering the next command).

* If I start typing a command while waiting for the previous command to finish, it seems to double part of the command that I'm typing (e.g., if I run git status, then type "git status" again while the first git status is running, the prompt displays "git statusgit status" when the first git status command finishes).

It's annoying enough that I've switched back to Git for Windows 2.26.2.

Matt

[Philip Oakley]

I'm seeing a similar thing

phili@Philip-Win10 MINGW64 /c/git-sdk-64/usr/src/git (docfixup2)
$ git version
git version 2.27.0.rc0.windows.1


If I try `git blame Makefile`  (which is suitably long), and do 6 space
bars and 'q', then I also get those 6 spaces and a q which if I press
return gives command not found, as below.

5e9637c6297 (Ævar Arnfjörð Bjarmason    2011-11-18 00:14:42 +0100   94)
# doesn'
t support GNU extensions like --check and --statistics
5e9637c6297 (Ævar Arnfjörð Bjarmason    2011-11-18 00:14:42 +0100   95) #

phili@Philip-Win10 MINGW64 /c/git-sdk-64/usr/src/git (docfixup2)
$       q
bash: q: command not found

phili@Philip-Win10 MINGW64 /c/git-sdk-64/usr/src/git (docfixup2)
$

At the moment it's a minor annoyance, but now it's been pointed out...

[Đoàn Trần Công Danh]

On 2020-05-19 13:16:40+0200, Johannes Schindelin <Johannes....@gmx.de> wrote:
> > > > To be honest, this time round I would _really_ like to ask for some manual
> > > > testing. I upgraded the MSYS2 runtime from being based on Cygwin v3.0.7 to
> > > > v3.1.4, and the biggest new feature is support for those new-fangled
> > > > pseudo terminals that Windows 10 now supports. I did find a couple of
> > > > rough edges in my use cases, but I am not exactly a typical Git for
> > > > Windows user...

Hi Dscho,

I've installed Git for Windows 2.27.0 rc0 in my $work_machine today,
I've run into this error during installation:

Cannot create file "<my %localappdata%>\Programs\Git\dev\fd".
Access is denied.

I have GfW 2.19.0 installed (by IT policy) in "%programfiles%\Git", and
GfW 2.26.2 installed in %localappdata%\Programs\Git. I don't have the
right to install software in my $work_machine

I can still use git-bash (by double-click git-bash.exe) after
installation, though.

If you want more information, please tell me,
I'll try to get it, tomorrow.

> > > > Could I ask for some manual testing in particular of anything run inside
> > > > the Git Bash?
> > >
> > >
> > > I’m happy to set it up and use it as my daily driver on one of my
> > > workstations, but I don’t want to overpromise how much help I can really
> > > offer for that sort of testing. I don’t do much of my full-time development
> > > on Windows anymore for a variety of reasons, so even if I install it in my
> > > Windows machines I won’t get that much active use in. And when I do use
> > > Windows, I keep my workflow pretty simple, so aside from basic adds and
> > > commits with an occasional checkout or very rare rebase, I just don’t cover
> > > that much functionality.
>
> Turns out that I ran into even more issues when trying to do a visual
> selection in `vim`: it would frequently "lose" the selection when I moved
> via the cursor keys.

My Windows machine is only used to run Ubuntu in a Virtual Box.
My limited exposure to GfW doesn't have any trouble.
My normal vim usage in GfW's git-bash works pretty well.
FWIW, I don't use arrow keys with vim.

> So I've come to the conclusion that the pseudo console support code is
> still too buggy to unleash onto Git for Windows' users, except as an
> experimental option. I will patch it to make the pseudo console feature
> opt-in instead of opt-out, and then also offer to configure it in Git for
> Windows' installer via an experimental option.
>
> Has anybody else run into issues with console programs (such as `vim`,
> interactive Bash, etc)? Or is there anybody with a very different
> experience than mine, i.e. _not_ having run into any issues despite using
> (interactively) Git Bash extensively?

Is there anything that you would like to have a cross-check,
I can check during my free time, I can't promise much since I mostly
work inside my Ubuntu virtual machine.

--
Danh