From: "Johannes Schindelin via GitGitGadget" <gitgitgadget@gmail•com>
To: git@vger•kernel.org
Cc: Junio C Hamano <gitster@pobox•com>
Subject: [PATCH 0/3] Handle worktrees at the top of a network drive
Date: Sat, 24 Aug 2019 15:10:44 -0700 (PDT) [thread overview]
Message-ID: <pull.141.git.gitgitgadget@gmail.com> (raw)
Windows' network drive concept is a quite useful and versatile one. Once
authenticated, one can even change the working directory to a network drive
(cd \\server\share, works in PowerShell and Git Bash).
Some users want to have their Git repositories there, and with these
patches, that works, even.
This is yet another patch series in the seemingly endless stream of Git for
Windows patches.
Johannes Schindelin (3):
setup_git_directory(): handle UNC paths correctly
Fix .git/ discovery at the root of UNC shares
setup_git_directory(): handle UNC root paths correctly
setup.c | 10 ++++++++--
1 file changed, 8 insertions(+), 2 deletions(-)
base-commit: 8104ec994ea3849a968b4667d072fedd1e688642
Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-141%2Fdscho%2Fgitdir-at-unc-root-v1
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-141/dscho/gitdir-at-unc-root-v1
Pull-Request: https://github.com/gitgitgadget/git/pull/141
--
gitgitgadget
next reply other threads:[~2019-08-24 22:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-24 22:10 Johannes Schindelin via GitGitGadget [this message]
2019-08-24 22:10 ` [PATCH 1/3] setup_git_directory(): handle UNC paths correctly Johannes Schindelin via GitGitGadget
2019-08-24 22:10 ` [PATCH 2/3] Fix .git/ discovery at the root of UNC shares Johannes Schindelin via GitGitGadget
2019-08-24 22:10 ` [PATCH 3/3] setup_git_directory(): handle UNC root paths correctly Johannes Schindelin via GitGitGadget
2019-08-26 17:08 ` [PATCH 0/3] Handle worktrees at the top of a network drive 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=pull.141.git.gitgitgadget@gmail.com \
--to=gitgitgadget@gmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=gitster@pobox$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox