All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: "brian m. carlson" <sandals@crustytoothpaste.net>
Cc: git@vger.kernel.org
Subject: Re: symbolic links in Git for Windows v2.27.0, was Re: [ANNOUNCE] Git for Windows 2.27.0-rc2
Date: Fri, 29 May 2020 15:40:03 +0200 (CEST)	[thread overview]
Message-ID: <nycvar.QRO.7.76.6.2005291539080.56@tvgsbejvaqbjf.bet> (raw)
In-Reply-To: <20200529223200.GJ1915090@camp.crustytoothpaste.net>

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

  reply	other threads:[~2020-05-30 11:41 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-26 20:45 [ANNOUNCE] Git for Windows 2.27.0-rc2 Johannes Schindelin
2020-05-28 21:35 ` symbolic links in Git for Windows v2.27.0, was " Johannes Schindelin
2020-05-29 17:23   ` Junio C Hamano
2020-05-29  5:56     ` Johannes Schindelin
2020-05-29 22:32   ` brian m. carlson
2020-05-29 13:40     ` Johannes Schindelin [this message]
2020-05-30 16:49       ` brian m. carlson
2020-05-30  8:03         ` Johannes Schindelin
2020-06-01 21:05   ` Junio C Hamano
2020-06-02 20:32     ` Johannes Schindelin
2020-06-02 21:17       ` Junio C Hamano
2020-06-03 13:54         ` Johannes Schindelin
2020-06-03 19:34           ` Junio C Hamano

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=nycvar.QRO.7.76.6.2005291539080.56@tvgsbejvaqbjf.bet \
    --to=johannes.schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=sandals@crustytoothpaste.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.