public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Takashi Yano <takashi.yano@nifty.ne.jp>
To: cygwin@cygwin.com
Subject: Re: 3.3.0: Possible regression in cygwin DLL (Win10); fixed in snapshot
Date: Fri, 5 Nov 2021 17:05:42 +0900	[thread overview]
Message-ID: <20211105170542.96ce6dd4ca32880ddfddd660@nifty.ne.jp> (raw)
In-Reply-To: <CAEv6GOA-y58YrftXgEgFrjqtOTHmfdu2Vrq76Lwn0suZpZ=U9w@mail.gmail.com>

On Thu, 4 Nov 2021 23:29:39 -0500
Brian wrote:
> I posted the steps needed to reproduce the problem in the following link:
> https://github.com/microsoft/Git-Credential-Manager-Core/issues/509. This
> includes the version of GCM-Core that was installed as well as how to
> reproduce the issue.
> 
> I also included detailed logs.
> 
> Was there something additional that you needed?

Yes.

I am not familiar with GCM core at all, so need more detailed steps.

Should I download gcmcore-win-x86-2.0.567.18224.exe and install it?
Or other than that?

How do you run it in cygwin?

Do you assume to associate cygwin git with GCM core?
Or do you use git in "Git for Windows" inside cygwin?

How should I setup git repository to use GCM core?

-- 
Takashi Yano <takashi.yano@nifty.ne.jp>

  parent reply	other threads:[~2021-11-05  8:06 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-04 15:02 Brian
2021-11-05  3:39 ` Takashi Yano
     [not found]   ` <CAEv6GOA-y58YrftXgEgFrjqtOTHmfdu2Vrq76Lwn0suZpZ=U9w@mail.gmail.com>
2021-11-05  8:05     ` Takashi Yano [this message]
2021-11-05 13:42       ` Brian
2021-11-05 19:41         ` Takashi Yano
2021-11-05 20:08           ` Ken Brown
2021-11-06 16:22             ` Ken Brown
2021-11-05 21:32           ` Brian
2021-11-06  6:24         ` ASSI
2021-11-08 16:30           ` Andrey Repin
2021-11-08 20:49             ` Adam Dinwoodie
2021-11-08 23:18               ` Brian Koontz

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=20211105170542.96ce6dd4ca32880ddfddd660@nifty.ne.jp \
    --to=takashi.yano@nifty.ne.jp \
    --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).