git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: git-for-windows@googlegroups.com, git@vger.kernel.org,
	git-packagers@googlegroups.com
Subject: symbolic links in Git for Windows v2.27.0, was Re: [ANNOUNCE] Git for Windows 2.27.0-rc2
Date: Thu, 28 May 2020 23:35:24 +0200 (CEST)	[thread overview]
Message-ID: <nycvar.QRO.7.76.6.2005282322580.56@tvgsbejvaqbjf.bet> (raw)
In-Reply-To: <20200526204539.6181-1-johannes.schindelin@gmx.de>

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


  reply	other threads:[~2020-05-29 14:09 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 ` Johannes Schindelin [this message]
2020-05-29 17:23   ` symbolic links in Git for Windows v2.27.0, was " 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
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

  List information: http://vger.kernel.org/majordomo-info.html

* 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.2005282322580.56@tvgsbejvaqbjf.bet \
    --to=johannes.schindelin@gmx.de \
    --cc=git-for-windows@googlegroups.com \
    --cc=git-packagers@googlegroups.com \
    --cc=git@vger.kernel.org \
    /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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).