Git for Windows v2.20.0-rc0, was Re: [ANNOUNCE] Git v2.20.0-rc0

[Johannes Schindelin]

Team,

On Sun, 18 Nov 2018, Junio C Hamano wrote:

> An early preview release Git v2.20.0-rc0 is now available for
> testing at the usual places. It is comprised of 887 non-merge
> commits since v2.19.0, contributed by 71 people, 23 of which are
> new faces.

The "for Windows" flavor of Git v2.20.0-rc0 is available here:

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

The current change log for v2.20.0 reads like this:

Changes since Git for Windows v2.19.1 (Oct 5th 2018)

Please note: Git CMD is deprecated as of this Git for Windows version. The
default is to have git.exe in the PATH anyway, so there is no noticeable
difference between CMD and Git CMD. It is impossible to turn off CMD's
behavior where it picks up any git.exe in the current directory, so let's
discourage the use of Git CMD. Users who dislike Git Bash should switch to
Powershell instead.

New Features

• Comes with OpenSSH v7.9p1.
• The description of the editor option to choose Vim has been clarified
to state that this unsets core.editor.
• Comes with cURL v7.62.0.
• The type of symlinks to create (directory or file) can now be
specified via the .gitattributes.
• The FSCache feature now uses a faster method to enumerate files,
making e.g. git status faster in large repositories.
• Comes with Git Credential Manager v1.18.3.
• Comes with Git LFS v2.6.0.
• Comes with MSYS2 runtime (Git for Windows flavor) based on Cygwin
2.11.2.
• The FSCache feature was optimized to become faster.

Bug Fixes

• The 64-bit Portable Git no longer sets pack.packSizeLimit.

Thanks,
Johannes

[Mateusz Łoskot]

On Tuesday, 20 November 2018 21:57:15 UTC+1, Johannes Schindelin wrote:

On Sun, 18 Nov 2018, Junio C Hamano wrote:

> An early preview release Git v2.20.0-rc0 is now available for
> testing at the usual places.  It is comprised of 887 non-merge
> commits since v2.19.0, contributed by 71 people, 23 of which are
> new faces.

The "for Windows" flavor of Git v2.20.0-rc0 is available here:

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

The current change log for v2.20.0 reads like this:

Changes since Git for Windows v2.19.1 (Oct 5th 2018)

Please note: Git CMD is deprecated as of this Git for Windows version. The
default is to have git.exe in the PATH anyway, so there is no noticeable
difference between CMD and Git CMD. It is impossible to turn off CMD's
behavior where it picks up any git.exe in the current directory, so let's
discourage the use of Git CMD. Users who dislike Git Bash should switch to
Powershell instead.

Hi,

Does this also mean the installer option to

"Use git from the Windows Command Prompt"

disappeared?

Or, has it been replaced with Powershell?

Best regards,

--

Mateusz Loskot, mat...@loskot.net

[Johannes Schindelin]

Hi Stefan,

On Thu, 22 Nov 2018, stefan...@atlas-elektronik.com wrote:

> Just a quick note:
>
> I installed v2.20.0-rc0 with these options:
>
> $ cat /etc/install-options.txt
> Editor Option: VIM
> Custom Editor Path:
> Path Option: Cmd
> SSH Option: OpenSSH
> CURL Option: OpenSSL
> CRLF Option: CRLFCommitAsIs
> Bash Terminal Option: MinTTY
> Performance Tweaks FSCache: Enabled
> Use Credential Manager: Enabled
> Enable Symlinks: Disabled
> Enable Builtin Rebase: Enabled
> Enable Builtin Stash: Enabled
>
>
>
> When starting the git bash two windows pop up instead of one.
> One that's "empty" and the other one containing the real git bash.

Thank you for the report. This has been also reported at
https://github.com/git-for-windows/git/issues/1942, and I fixed it in the
meantime.

Ciao,
Johannes

>
> Thanks,
> Stefan

> --
> ----------------------------------------------------------------
> /dev/random says: To save trouble later, Joe named his cat Roadkill Fred
> python -c "print '73746566616e2e6e616577654061746c61732d656c656b74726f6e696b2e636f6d'.decode('hex')"
> GPG Key fingerprint = 2DF5 E01B 09C3 7501 BCA9 9666 829B 49C5 9221 27AF

[Johannes Schindelin]

Hi Mateusz,

On Tue, 20 Nov 2018, Mateusz Łoskot wrote:

> On Tuesday, 20 November 2018 21:57:15 UTC+1, Johannes Schindelin wrote:
> >
> > Please note: Git CMD is deprecated as of this Git for Windows version.
> > The default is to have git.exe in the PATH anyway, so there is no
> > noticeable difference between CMD and Git CMD. It is impossible to
> > turn off CMD's behavior where it picks up any git.exe in the current
> > directory, so let's discourage the use of Git CMD. Users who dislike
> > Git Bash should switch to Powershell instead.
>

> Does this also mean the installer option to "Use git from the Windows
> Command Prompt" disappeared?

No, this is the default I talked about when I said "The default is to have
git.exe in the PATH anyway".

> Or, has it been replaced with Powershell?

That setting "Use Git from the Windows Command Prompt" affected PowerShell
already: by "Windows Command Prompt", I refer to both CMD and PowerShell:
both are Windows Command Prompts.

BTW the issue that triggered that "Git CMD is deprecated" work is really
that if you call `git show HEAD` in a CMD and there is a `git.exe` in the
current directory, that `git.exe` is used instead of the one on the PATH.

But a Git user had a really great idea: using DOSKEY in Git CMD to force
`git show HEAD` to pick up the correct `git.exe`. And this will be part of
the next Git for Windows version.

The only remaining question is: should I "un-deprecate" Git CMD now?

Ciao,
Johannes

[Mateusz Loskot]

Hi Johannes,

On Fri, 23 Nov 2018 at 10:26, Johannes Schindelin
<Johannes....@gmx.de> wrote:
> On Tue, 20 Nov 2018, Mateusz Łoskot wrote:
> > On Tuesday, 20 November 2018 21:57:15 UTC+1, Johannes Schindelin wrote:
> > >
> > > Please note: Git CMD is deprecated as of this Git for Windows version.
> > > The default is to have git.exe in the PATH anyway, so there is no
> > > noticeable difference between CMD and Git CMD. It is impossible to
> > > turn off CMD's behavior where it picks up any git.exe in the current
> > > directory, so let's discourage the use of Git CMD. Users who dislike
> > > Git Bash should switch to Powershell instead.
> >
> > Does this also mean the installer option to "Use git from the Windows
> > Command Prompt" disappeared?
>
> No, this is the default I talked about when I said "The default is to have
> git.exe in the PATH anyway".

I see.

> > Or, has it been replaced with Powershell?
>
> That setting "Use Git from the Windows Command Prompt" affected PowerShell
> already: by "Windows Command Prompt", I refer to both CMD and PowerShell:
> both are Windows Command Prompts.

Please, forgive me the teaching tone, but your use of
the "Windows Command Prompt" is/may be confusing to Windows users.
It was to me, hence my questions.

Capitalised "Command Prompt" is an own name of the prompt running cmd.exe.
When a Windows user goes START > Windows System > Command Prompt,
she runs cmd.exe, not PowerShell.
Shortly, there are two native command prompts in Windows with distinct names:
- Command Prompt
- Windows PowerShell

> BTW the issue that triggered that "Git CMD is deprecated" work is really
> that if you call `git show HEAD` in a CMD and there is a `git.exe` in the
> current directory, that `git.exe` is used instead of the one on the PATH.
>
> But a Git user had a really great idea: using DOSKEY in Git CMD to force
> `git show HEAD` to pick up the correct `git.exe`. And this will be part of
> the next Git for Windows version.

Thank you for the explanation.

> The only remaining question is: should I "un-deprecate" Git CMD now?

To me, no.

Best regards,
--
Mateusz Loskot, http://mateusz.loskot.net

[Johannes Schindelin]

Hi Mateusz,

On Fri, 23 Nov 2018, Mateusz Loskot wrote:

> On Fri, 23 Nov 2018 at 10:26, Johannes Schindelin
> <Johannes....@gmx.de> wrote:
> > On Tue, 20 Nov 2018, Mateusz Łoskot wrote:
> >
> > > Or, has it been replaced with Powershell?
> >
> > That setting "Use Git from the Windows Command Prompt" affected PowerShell
> > already: by "Windows Command Prompt", I refer to both CMD and PowerShell:
> > both are Windows Command Prompts.
>
> Please, forgive me the teaching tone, but your use of
> the "Windows Command Prompt" is/may be confusing to Windows users.

No offense taken.

What I *would* like to take is a Pull Request where you edit the
respective part of the installer:
https://github.com/git-for-windows/build-extra/blob/c34eef778eab72a09cbcf7f0e4cb69047058fc0b/installer/install.iss#L1439

Thanks,
Johannes

[Mateusz Loskot]

On Fri, 23 Nov 2018 at 13:02, Johannes Schindelin

<Johannes....@gmx.de> wrote:
> On Fri, 23 Nov 2018, Mateusz Loskot wrote:
> > On Fri, 23 Nov 2018 at 10:26, Johannes Schindelin <Johannes....@gmx.de> wrote:
> > > On Tue, 20 Nov 2018, Mateusz Łoskot wrote:
> > > > Or, has it been replaced with Powershell?
> > >
> > > That setting "Use Git from the Windows Command Prompt" affected PowerShell
> > > already: by "Windows Command Prompt", I refer to both CMD and PowerShell:
> > > both are Windows Command Prompts.
> >
> > Please, forgive me the teaching tone, but your use of
> > the "Windows Command Prompt" is/may be confusing to Windows users.
>
> No offense taken.
>
> What I *would* like to take is a Pull Request where you edit the
> respective part of the installer:
> https://github.com/git-for-windows/build-extra/blob/c34eef778eab72a09cbcf7f0e4cb69047058fc0b/installer/install.iss#L1439

https://github.com/git-for-windows/build-extra/pull/216

Although the little naming discussion was spawned by my confusion,
later clarified in this thread, I don't think there is reason to die hard for
fixing the names - esp. there is little or no truly authoritative
resources on that.
I submitted this PR mostly for the records, for some sort of a closure :)

[Johannes Schindelin]

Hi Mateusz,

Thank you for opening this PR. I see a lot of value in it, maybe even more
than you do ;-)

Ciao,
Johannes

>
> Best regards,
> --
> Mateusz Loskot, http://mateusz.loskot.net
>

> --
> 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 post to this group, send email to git-for...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/git-for-windows/CABUeae8B30YSVvjtRG1kaGz_MiHJX-bPvz%2Bx3Ff9HCee4Fy6Vg%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.
>

[Mateusz Loskot]

Hi Johannes,


On Wed, 28 Nov 2018 at 09:59, Johannes Schindelin

<Johannes....@gmx.de> wrote:
> On Tue, 27 Nov 2018, Mateusz Loskot wrote:
> > On Fri, 23 Nov 2018 at 13:02, Johannes Schindelin <Johannes....@gmx.de> wrote:
> > > On Fri, 23 Nov 2018, Mateusz Loskot wrote:
> > > > On Fri, 23 Nov 2018 at 10:26, Johannes Schindelin <Johannes....@gmx.de> wrote:
> > > > > On Tue, 20 Nov 2018, Mateusz Łoskot wrote:
> > > > > > Or, has it been replaced with Powershell?
> > > > >
> > > > > That setting "Use Git from the Windows Command Prompt" affected PowerShell
> > > > > already: by "Windows Command Prompt", I refer to both CMD and PowerShell:
> > > > > both are Windows Command Prompts.
> > > >
> > > > Please, forgive me the teaching tone, but your use of
> > > > the "Windows Command Prompt" is/may be confusing to Windows users.
> > >
> > > No offense taken.
> > >
> > > What I *would* like to take is a Pull Request where you edit the
> > > respective part of the installer:
> > > https://github.com/git-for-windows/build-extra/blob/c34eef778eab72a09cbcf7f0e4cb69047058fc0b/installer/install.iss#L1439
> >
> > https://github.com/git-for-windows/build-extra/pull/216
> >
> > Although the little naming discussion was spawned by my confusion,
> > later clarified in this thread, I don't think there is reason to die hard for
> > fixing the names - esp. there is little or no truly authoritative
> > resources on that.
> > I submitted this PR mostly for the records, for some sort of a closure :)
>
> Thank you for opening this PR. I see a lot of value in it, maybe even more
> than you do ;-)

I'm glad we've sorted the wording out :) Thanks for the assitance.