[ANNOUNCE] Git for Windows 2.27.0-rc2

[ANNOUNCE] Git for Windows 2.27.0-rc2

[Johannes Schindelin]

Dear Git users,

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

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

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

This release comes with a Git Bash that optionally uses Windows-native
pseudo consoles. Meaning: finally, Git Bash can accommodate console
programs like node.exe, Python or PHP, without using the winpty helper
(see Known Issues above). Note that this is still a very new feature
and is therefore known to have some corner-case bugs.

New Features

  * Comes with Git v2.27.0-rc2.
  * Comes with OpenSSL v1.1.1g.
  * 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 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-rc2-64-bit.exe | 5fff39a4563d9bcfdf77946adef06781ae77433ca09ff6afaae5f9398ec071cb
Git-2.27.0-rc2-32-bit.exe | 5a9ddc85a99c048cd89a329e9353ef31ac36532d0fd274f7413bf0ee7710f81d
PortableGit-2.27.0-rc2-64-bit.7z.exe | ac0665a5739d939eecd37d475091b38ed6e0535cbda92f1a53385cd46bed8904
PortableGit-2.27.0-rc2-32-bit.7z.exe | f2151bb3804aadeb44e2e1047113b38540305ad3bd5e7f2598c8db004b0bf834
MinGit-2.27.0-rc2-64-bit.zip | 7948a5ec291fb73ad3af1fbacaeebb234fb1926915a69e2e927aabb436b51f8b
MinGit-2.27.0-rc2-32-bit.zip | f47b9b3869cb072518c7e971a2709b3c5659d4bc35867fab0a117c392f395eaf
MinGit-2.27.0-rc2-busybox-64-bit.zip | af7b9e1da84ed21bff6d4dac3fdf4ca9dfd5788d7238ac6fda759bbe5fb7f875
MinGit-2.27.0-rc2-busybox-32-bit.zip | 16f3f8b90bfeed191db11c18995169380db0d34a45ff5a3004d5434acef98d58
Git-2.27.0-rc2-64-bit.tar.bz2 | b1275d236ff7c4de3d713deefc326120b07ba9a4d32761bf2216364be10a8867
Git-2.27.0-rc2-32-bit.tar.bz2 | 24993d2abbe7c75d3bb0557550366f919ee10750733c0fd9e05b6ff7c8180c7a

Ciao,
Johannes

symbolic links in Git for Windows v2.27.0, was Re: [ANNOUNCE] Git for Windows 2.27.0-rc2

[Johannes Schindelin]

Dear Git users,

On Tue, 26 May 2020, Johannes Schindelin wrote:

> I hereby announce that Git for Windows 2.27.0-rc2 is available from:
>
>     https://github.com/git-for-windows/git/releases/tag/v2.27.0-rc2.windows.1

Git for Windows v2.27.0 will be out on Tuesday (or even on Monday if Git
v2.27.0 is released early enough). It has a (last-minute) bug fix where
the length of symbolic links that is recorded in the Git index is the
_actual_ length of the link target, so that `git status` agrees between
Git for Windows and WSL Git.

Unfortunately, that means that every existing checkout that contains
symbolic links tracked by Git will report them as changed until `git add
<path-to-symlink>` (or `git add -u`) is called.

In cases where users use both Git Bash and another version of Git, this
might cause the problem where one of them will always report the symbolic
links as modified in `git status`, but not in `git diff`.

Sorry about the late heads-up, I only just realized that this might pose a
problem. Granted, symbolic links are not all _that_ common on Windows.

Ciao,
Johannes

Re: symbolic links in Git for Windows v2.27.0, was Re: [ANNOUNCE] Git for Windows 2.27.0-rc2

[Junio C Hamano]

Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:

> Dear Git users,
>
> On Tue, 26 May 2020, Johannes Schindelin wrote:
>
>> I hereby announce that Git for Windows 2.27.0-rc2 is available from:
>>
>>     https://github.com/git-for-windows/git/releases/tag/v2.27.0-rc2.windows.1
>
> Git for Windows v2.27.0 will be out on Tuesday (or even on Monday if Git
> v2.27.0 is released early enough). It has a (last-minute) bug fix where
> the length of symbolic links that is recorded in the Git index is the
> _actual_ length of the link target, so that `git status` agrees between
> Git for Windows and WSL Git.
>
> Unfortunately, that means that every existing checkout that contains
> symbolic links tracked by Git will report them as changed until `git add
> <path-to-symlink>` (or `git add -u`) is called.

So, this is not something "git update-index --refresh" would be able
to fix?

>
> In cases where users use both Git Bash and another version of Git, this
> might cause the problem where one of them will always report the symbolic
> links as modified in `git status`, but not in `git diff`.
>
> Sorry about the late heads-up, I only just realized that this might pose a
> problem. Granted, symbolic links are not all _that_ common on Windows.
>
> Ciao,
> Johannes

Re: symbolic links in Git for Windows v2.27.0, was Re: [ANNOUNCE] Git for Windows 2.27.0-rc2

[Johannes Schindelin]

Hi Junio,

On Fri, 29 May 2020, Junio C Hamano wrote:

> Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
>
> > Dear Git users,
> >
> > On Tue, 26 May 2020, Johannes Schindelin wrote:
> >
> >> I hereby announce that Git for Windows 2.27.0-rc2 is available from:
> >>
> >>     https://github.com/git-for-windows/git/releases/tag/v2.27.0-rc2.windows.1
> >
> > Git for Windows v2.27.0 will be out on Tuesday (or even on Monday if Git
> > v2.27.0 is released early enough). It has a (last-minute) bug fix where
> > the length of symbolic links that is recorded in the Git index is the
> > _actual_ length of the link target, so that `git status` agrees between
> > Git for Windows and WSL Git.
> >
> > Unfortunately, that means that every existing checkout that contains
> > symbolic links tracked by Git will report them as changed until `git add
> > <path-to-symlink>` (or `git add -u`) is called.
>
> So, this is not something "git update-index --refresh" would be able
> to fix?

I just tested this, and no, it does not fix the issue.

The bug in question records the length of _any_ symbolic link as 4096 in
the index, and an `update-index --refresh` with a fixed version of Git
apparently does not update that (the contents did _not_ change, after all).

Ciao,
Dscho

>
> >
> > In cases where users use both Git Bash and another version of Git, this
> > might cause the problem where one of them will always report the symbolic
> > links as modified in `git status`, but not in `git diff`.
> >
> > Sorry about the late heads-up, I only just realized that this might pose a
> > problem. Granted, symbolic links are not all _that_ common on Windows.
> >
> > Ciao,
> > Johannes
>

Re: symbolic links in Git for Windows v2.27.0, was Re: [ANNOUNCE] Git for Windows 2.27.0-rc2

[brian m. carlson]

[-- Attachment #1: Type: text/plain, Size: 887 bytes --]

On 2020-05-28 at 21:35:24, Johannes Schindelin wrote:
> Dear Git users,
> 
> On Tue, 26 May 2020, Johannes Schindelin wrote:
> 
> > I hereby announce that Git for Windows 2.27.0-rc2 is available from:
> >
> >     https://github.com/git-for-windows/git/releases/tag/v2.27.0-rc2.windows.1
> 
> Git for Windows v2.27.0 will be out on Tuesday (or even on Monday if Git
> v2.27.0 is released early enough). It has a (last-minute) bug fix where
> the length of symbolic links that is recorded in the Git index is the
> _actual_ length of the link target, so that `git status` agrees between
> Git for Windows and WSL Git.

Thank you for this.  While I don't usually use Windows, this has been a
pain point for a lot of Windows users, and fixing it will significantly
improve the user experience.
-- 
brian m. carlson: Houston, Texas, US
OpenPGP: https://keybase.io/bk2204

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 263 bytes --]

Re: symbolic links in Git for Windows v2.27.0, was Re: [ANNOUNCE] Git for Windows 2.27.0-rc2

[Johannes Schindelin]

Hi brian,

On Fri, 29 May 2020, brian m. carlson wrote:

> On 2020-05-28 at 21:35:24, Johannes Schindelin wrote:
> > Dear Git users,
> >
> > On Tue, 26 May 2020, Johannes Schindelin wrote:
> >
> > > I hereby announce that Git for Windows 2.27.0-rc2 is available from:
> > >
> > >     https://github.com/git-for-windows/git/releases/tag/v2.27.0-rc2.windows.1
> >
> > Git for Windows v2.27.0 will be out on Tuesday (or even on Monday if Git
> > v2.27.0 is released early enough). It has a (last-minute) bug fix where
> > the length of symbolic links that is recorded in the Git index is the
> > _actual_ length of the link target, so that `git status` agrees between
> > Git for Windows and WSL Git.
>
> Thank you for this.  While I don't usually use Windows, this has been a
> pain point for a lot of Windows users, and fixing it will significantly
> improve the user experience.

To be quite honest, I had no idea that it was a pain point, as it did not
come up on the Git for Windows tracker.

Do you have a list of pain points on Windows that you're aware of? I would
love to get my hands on it to triage, prioritize, and address those
issues.

Thanks,
Dscho

Re: symbolic links in Git for Windows v2.27.0, was Re: [ANNOUNCE] Git for Windows 2.27.0-rc2

[brian m. carlson]

[-- Attachment #1: Type: text/plain, Size: 1102 bytes --]

On 2020-05-29 at 13:40:03, Johannes Schindelin wrote:
> To be quite honest, I had no idea that it was a pain point, as it did not
> come up on the Git for Windows tracker.
> 
> Do you have a list of pain points on Windows that you're aware of? I would
> love to get my hands on it to triage, prioritize, and address those
> issues.

No, I don't, but I've seen this particular issue on Stack Overflow
probably four or five times and answered it each time.  I didn't think
to look at the Git for Windows issue tracker, since I just considered it
a difference between how Windows and Linux report symbolic links, not
something that could theoretically be fixed.  Obviously I was wrong.

If I see more Windows-related problems show up on Stack Overflow that
aren't on the issue tracker, I'll send folks your way to report them.  I
want to assure you that I'm not intentionally depriving you of the
information you need to fix problems; in this case, I just didn't think
of it as a thing that could be fixed.
-- 
brian m. carlson: Houston, Texas, US
OpenPGP: https://keybase.io/bk2204

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 263 bytes --]

Re: symbolic links in Git for Windows v2.27.0, was Re: [ANNOUNCE] Git for Windows 2.27.0-rc2

[Johannes Schindelin]

Hi brian,

On Sat, 30 May 2020, brian m. carlson wrote:

> On 2020-05-29 at 13:40:03, Johannes Schindelin wrote:
> > To be quite honest, I had no idea that it was a pain point, as it did not
> > come up on the Git for Windows tracker.
> >
> > Do you have a list of pain points on Windows that you're aware of? I would
> > love to get my hands on it to triage, prioritize, and address those
> > issues.
>
> No, I don't, but I've seen this particular issue on Stack Overflow
> probably four or five times and answered it each time.  I didn't think
> to look at the Git for Windows issue tracker, since I just considered it
> a difference between how Windows and Linux report symbolic links, not
> something that could theoretically be fixed.  Obviously I was wrong.

Ah, that makes sense. To be honest, I did share your expectation that this
is simply something that cannot be fixed. Imagine my delight at seeing
myself being proven wrong ;-)

> If I see more Windows-related problems show up on Stack Overflow that
> aren't on the issue tracker, I'll send folks your way to report them.  I
> want to assure you that I'm not intentionally depriving you of the
> information you need to fix problems; in this case, I just didn't think
> of it as a thing that could be fixed.

Oh, I guessed that it was that (or lack of time). Thank you for
considering to suggest bug reports in the Git for Windows bug tracker.

Ciao,
Dscho

Re: symbolic links in Git for Windows v2.27.0, was Re: [ANNOUNCE] Git for Windows 2.27.0-rc2

[Junio C Hamano]

Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:

> Git for Windows v2.27.0 will be out on Tuesday (or even on Monday if Git
> v2.27.0 is released early enough).

Thanks for a reminder that Europe is ahead of me by about a bit less
than half a day ;-)

Re: symbolic links in Git for Windows v2.27.0, was Re: [ANNOUNCE] Git for Windows 2.27.0-rc2

[Johannes Schindelin]

Hi Junio,

On Mon, 1 Jun 2020, Junio C Hamano wrote:

> Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
>
> > Git for Windows v2.27.0 will be out on Tuesday (or even on Monday if Git
> > v2.27.0 is released early enough).
>
> Thanks for a reminder that Europe is ahead of me by about a bit less
> than half a day ;-)

You're welcome ;-)
Dscho

Re: symbolic links in Git for Windows v2.27.0, was Re: [ANNOUNCE] Git for Windows 2.27.0-rc2

[Junio C Hamano]

Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:

>> Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
>>
>> > Git for Windows v2.27.0 will be out on Tuesday (or even on Monday if Git
>> > v2.27.0 is released early enough).
>>
>> Thanks for a reminder that Europe is ahead of me by about a bit less
>> than half a day ;-)
>
> You're welcome ;-)

I'll remind myself that I'll try to tag and push out the final
before 1700 UTC, which would be around 10AM for me ;-)

Re: symbolic links in Git for Windows v2.27.0, was Re: [ANNOUNCE] Git for Windows 2.27.0-rc2

[Johannes Schindelin]

Hi Junio,

On Tue, 2 Jun 2020, Junio C Hamano wrote:

> Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
>
> >> Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> >>
> >> > Git for Windows v2.27.0 will be out on Tuesday (or even on Monday if Git
> >> > v2.27.0 is released early enough).
> >>
> >> Thanks for a reminder that Europe is ahead of me by about a bit less
> >> than half a day ;-)
> >
> > You're welcome ;-)
>
> I'll remind myself that I'll try to tag and push out the final
> before 1700 UTC, which would be around 10AM for me ;-)

That will work. That's 7pm for me, which is still safely after-hours, but
it's better than 2am.

On the other hand, I do not even think that Git for Windows versions
_need_ to be released on the same calendar day as Git versions.

For v2.27.0, for example, in hindsight I would have preferred to wait
until the next day so that I could have tested it much more thoroughly.
The symbolic link stuff we were talking about does not work correctly, and
I had missed that because I just "rushed out" a release on what was a
holiday for me.

So while I appreciate your concern, I think you need not bend over all
that much, it is not necessary.

Thank you!
Dscho

Re: symbolic links in Git for Windows v2.27.0, was Re: [ANNOUNCE] Git for Windows 2.27.0-rc2

[Junio C Hamano]

Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:

>> I'll remind myself that I'll try to tag and push out the final
>> before 1700 UTC, which would be around 10AM for me ;-)
>
> That will work. That's 7pm for me, which is still safely after-hours, but
> it's better than 2am.

That time is 2AM for me depending on the season, though I am
straying off of my migratory patterns this year.

> On the other hand, I do not even think that Git for Windows versions
> _need_ to be released on the same calendar day as Git versions.

True.  The "same calendar day" is a fuzzy notion anyway, and the
other major platform seems to lag by a lot more if I am not
mistaken.

I was just trying to make the schedule predictable, so that you and
others do not have to say "if the tag was pushed early enough in the
day for me".  I'd actually prefer to tag a bit later in the day
myself, so we can pick any time, or pick no time at all and have you
and distro folks subscribed to push notification RSS, perhaps.