From: Andrey Repin <anrdaemon@yandex.ru>
To: Brian Inglis <cygwin@cygwin.com>, cygwin@cygwin.com
Subject: Re: misterious GIT failure (SOLVED)
Date: Sun, 17 Jan 2021 21:11:18 +0300 [thread overview]
Message-ID: <449114268.20210117211118@yandex.ru> (raw)
In-Reply-To: <03cc5513-8a2c-d9cc-6b71-e0c2df0125ed@SystematicSw.ab.ca>
Greetings, Brian Inglis!
> On Friday, January 15, 2021, 11:36:28 AM EST, matthew patton via Cygwin wrote:
>> On 2021-01-15 10:09, matthew patton via Cygwin wrote:
>>> Ken Brown wrote:
>>>> Do you by any chance have symlinks in your PATH? There was a problem
>>>> reported in early December in which STATUS_IO_REPARSE_TAG_NOT_HANDLED
>>>> would sometimes occur when there was a symlink in PATH:
>>> Yes, the first and 3rd entries are symlinks. I've had these symlinks in my
>>> PATH for years.
>>> /home/MP1116/.aws/YYY/bin:/home/MP1116/bin -> .WPHOME/bin/
>>> .aws -> .WPHOME/.aws/.WPHOME -> Dropbox/Work_Projects/XXX
>>> # /etc/fstab
>>> C:/Users /home none binary,user 0 0
>> I excised the 2 symlink-involved PATH elements and now Git runs great with
>> v3.1.5 of the DLL. I'll try one of the snapshots at some point, but I am also
>> tempted to change my Bash function 'addPath()' to fully unroll symlinks
>> before adding.
>> https://github.com/tb3088/shell-environment/blob/master/.functions#L144
> Resolving Cygwin paths is best done using readlink or realpath followed by
> cygpath -alm then cygpath -auU to get canonical paths, as neither realpath nor
> cygpath do the complete job under Cygwin.
Can you provide examples? I find cygpath output satisfying so far, with
readlink if needs that bad.
--
With best regards,
Andrey Repin
Sunday, January 17, 2021 21:10:35
Sorry for my terrible english...
next prev parent reply other threads:[~2021-01-17 18:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1742171701.1391964.1610730544471.ref@mail.yahoo.com>
2021-01-15 17:09 ` matthew patton
2021-01-15 17:29 ` Brian Inglis
2021-01-17 18:11 ` Andrey Repin [this message]
2021-01-17 19:41 ` Brian Inglis
2021-01-17 21:07 ` matthew patton
2021-01-17 22:24 ` David Dyck
2021-01-15 17:48 ` Ken Brown
2021-01-16 17:22 ` matthew patton
2021-01-16 17:35 ` Ken Brown
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=449114268.20210117211118@yandex.ru \
--to=anrdaemon@yandex.ru \
--cc=cygwin@cygwin.com \
/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 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).