From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: misterious GIT failure (SOLVED)
Date: Fri, 15 Jan 2021 12:48:03 -0500 [thread overview]
Message-ID: <7bffd19d-23b0-e33e-5877-a9c1c010a187@cornell.edu> (raw)
In-Reply-To: <1742171701.1391964.1610730544471@mail.yahoo.com>
On 1/15/2021 12:09 PM, matthew patton via Cygwin wrote:
> 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,
You've almost certainly run into the same bug that was fixed in
https://sourceware.org/git/?p=newlib-cygwin.git;a=commit;h=aec6479820fee5f71d50930bf0dde2bbf386bd4b,
but it would be appreciated if you would confirm this by testing a snapshot.
Ken
next prev parent reply other threads:[~2021-01-15 17:48 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 [this message]
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=7bffd19d-23b0-e33e-5877-a9c1c010a187@cornell.edu \
--to=kbrown@cornell.edu \
--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).