All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Johannes Schindelin via GitGitGadget" <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org,  Johannes Schindelin <johannes.schindelin@gmx.de>
Subject: Re: [PATCH] mingw: skip symlink type auto-detection for network share targets
Date: Tue, 28 Jul 2026 15:45:02 -0700	[thread overview]
Message-ID: <xmqqcxw6d98x.fsf@gitster.g> (raw)
In-Reply-To: <pull.2189.git.1785239196007.gitgitgadget@gmail.com> (Johannes Schindelin via GitGitGadget's message of "Tue, 28 Jul 2026 11:46:35 +0000")

"Johannes Schindelin via GitGitGadget" <gitgitgadget@gmail.com>
writes:

> From: Johannes Schindelin <johannes.schindelin@gmx.de>
>
> On Windows, symbolic links come in two flavors: file symlinks and
> directory symlinks.  Since Git was born on Linux where this distinction
> does not exist, Git for Windows has to auto-detect the type by looking
> at the target.  When the target does not yet exist at symlink creation
> time, Git for Windows creates a "phantom" file symlink and later, once
> checkout is complete, calls `CreateFileW()` on the target to check
> whether it is actually a directory.
> ...
> Note that there are legitimate paths starting with a single backslash
> that are _not_ network paths: drive-less absolute paths are interpreted
> as relative to the current working directory's drive. In practice, these
> are highly uncommon (and brittle, just one working directory change away
> from breaking). In any case, the only consequence is now that the
> symlink type of those has to be specified via Git attributes, is all.

Thanks, will queue.

      reply	other threads:[~2026-07-28 22:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-28 11:46 [PATCH] mingw: skip symlink type auto-detection for network share targets Johannes Schindelin via GitGitGadget
2026-07-28 22:45 ` Junio C Hamano [this message]

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=xmqqcxw6d98x.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=gitgitgadget@gmail.com \
    --cc=johannes.schindelin@gmx.de \
    /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.