From: Ken Brown <kbrown@cornell.edu>
To: matthew patton <pattonme@yahoo.com>,
"cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: misterious GIT failure (SOLVED)
Date: Sat, 16 Jan 2021 12:35:18 -0500 [thread overview]
Message-ID: <5ad17aad-6d40-c6b7-a5d3-5e5be547466b@cornell.edu> (raw)
In-Reply-To: <1118056620.1572623.1610817748968@mail.yahoo.com>
On 1/16/2021 12:22 PM, matthew patton wrote:
> On Friday, January 15, 2021, 12:48:16 PM EST, Ken Brown via Cygwin
> <cygwin@cygwin.com> wrote:
> > but it would be appreciated if you would confirm this by testing a snapshot.
>
> I have confirmed that running snapshot build Cygwin1.dll from 2021-01-13 handles
> symlinks in the PATH as expected.
Thanks for testing!
Ken
prev parent reply other threads:[~2021-01-16 17:35 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
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 [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=5ad17aad-6d40-c6b7-a5d3-5e5be547466b@cornell.edu \
--to=kbrown@cornell.edu \
--cc=cygwin@cygwin.com \
--cc=pattonme@yahoo.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).