From: "Bret Barkelew" <bret.barkelew@microsoft.com>
To: Rebecca Cran <rebecca@bsdio.com>,
"rfc@edk2.groups.io" <rfc@edk2.groups.io>,
"lersek@redhat.com" <lersek@redhat.com>,
Andrew Fish <afish@apple.com>,
Michael Kubacki <Michael.Kubacki@microsoft.com>
Cc: "devel@edk2.groups.io" <devel@edk2.groups.io>,
"spbrogan@outlook.com" <spbrogan@outlook.com>,
"Desimone, Nathaniel L" <nathaniel.l.desimone@intel.com>,
"Kinney, Michael D" <michael.d.kinney@intel.com>,
"Leif Lindholm (Nuvia address)" <leif@nuviainc.com>
Subject: Re: [EXTERNAL] [edk2-devel] [edk2-rfc] GitHub Pull Request based Code Review Process
Date: Thu, 28 May 2020 06:57:44 +0000 [thread overview]
Message-ID: <CY4PR21MB0743B77264CD589D6F518299EF8E0@CY4PR21MB0743.namprd21.prod.outlook.com> (raw)
In-Reply-To: <CY4PR21MB07436C618910B33AFF9E0B76EFB10@CY4PR21MB0743.namprd21.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 2658 bytes --]
Rebecca,
I was able to confirm that it was an issue with Git for Windows. Looks like it’s fixed in current snapshots and will be in the next release:
https://github.com/git-for-windows/git/issues/2598
Also, ATTN: @Michael Kubacki<mailto:Michael.Kubacki@microsoft.com>
- Bret
From: Bret Barkelew<mailto:Bret.Barkelew@microsoft.com>
Sent: Wednesday, May 27, 2020 10:45 AM
To: Rebecca Cran<mailto:rebecca@bsdio.com>; rfc@edk2.groups.io<mailto:rfc@edk2.groups.io>; lersek@redhat.com<mailto:lersek@redhat.com>; Andrew Fish<mailto:afish@apple.com>
Cc: devel@edk2.groups.io<mailto:devel@edk2.groups.io>; spbrogan@outlook.com<mailto:spbrogan@outlook.com>; Desimone, Nathaniel L<mailto:nathaniel.l.desimone@intel.com>; Kinney, Michael D<mailto:michael.d.kinney@intel.com>; Leif Lindholm (Nuvia address)<mailto:leif@nuviainc.com>
Subject: RE: [EXTERNAL] [edk2-devel] [edk2-rfc] GitHub Pull Request based Code Review Process
That’s not a bad idea: I should try with my WSL install.
I’m on the same version of Git for Windows, and think I’ll open it as an issue to the maintainer.
For now, going though the paces is just as useful to me as getting a viable environment (after all, PRs soon!), so I don’t mind trying another OS or install if that’s what it takes.
- Bret
From: Rebecca Cran<mailto:rebecca@bsdio.com>
Sent: Wednesday, May 27, 2020 9:07 AM
To: rfc@edk2.groups.io<mailto:rfc@edk2.groups.io>; lersek@redhat.com<mailto:lersek@redhat.com>; Bret Barkelew<mailto:Bret.Barkelew@microsoft.com>; Andrew Fish<mailto:afish@apple.com>
Cc: devel@edk2.groups.io<mailto:devel@edk2.groups.io>; spbrogan@outlook.com<mailto:spbrogan@outlook.com>; Desimone, Nathaniel L<mailto:nathaniel.l.desimone@intel.com>; Kinney, Michael D<mailto:michael.d.kinney@intel.com>; Leif Lindholm (Nuvia address)<mailto:leif@nuviainc.com>
Subject: Re: [EXTERNAL] [edk2-devel] [edk2-rfc] GitHub Pull Request based Code Review Process
On 5/27/2020 6:12 AM, Laszlo Ersek wrote:
> So, it could be a MINGW64 packaging bug, perhaps.
I'm getting the same error, but with a different packaging of Git:
mine's in C:\Program Files\Git\cmd\git.exe .
It's version "git version 2.26.2.windows.1".
Of course it's possible it's just the same MINGW version that's been put
into its own installer.
I also tried using my openSUSE WSL installation, but it failed with:
STARTTLS failed! SSL connect attempt failed error:1416F086:SSL
routines:tls_process_server_certificate:certificate verify failed at
/usr/lib/git/git-send-email line 1548.
So I ended up copying it to one of my FreeBSD systems and sent it from
there.
--
Rebecca Cran
[-- Attachment #2: Type: text/html, Size: 5757 bytes --]
next prev parent reply other threads:[~2020-05-28 6:57 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-19 7:21 [edk2-devel] [edk2-rfc] GitHub Pull Request based Code Review Process Nate DeSimone
2020-05-19 8:39 ` Laszlo Ersek
2020-05-19 18:02 ` Nate DeSimone
2020-05-19 16:54 ` Sean
2020-05-19 18:02 ` Nate DeSimone
2020-05-19 19:34 ` Bret Barkelew
2020-05-19 19:59 ` Nate DeSimone
2020-05-19 20:10 ` Bret Barkelew
2020-05-19 21:02 ` Nate DeSimone
2020-05-19 21:07 ` Bret Barkelew
2020-05-20 17:05 ` Laszlo Ersek
2020-05-20 17:21 ` Sean
2020-05-22 1:56 ` Andrew Fish
2020-05-20 21:53 ` Laszlo Ersek
2020-05-22 5:31 ` [EXTERNAL] " Bret Barkelew
2020-05-19 21:22 ` Laszlo Ersek
2020-05-19 21:35 ` Nate DeSimone
2020-05-19 21:38 ` Bret Barkelew
2020-05-19 20:41 ` Laszlo Ersek
2020-05-19 22:25 ` Sean
2020-05-21 13:30 ` Laszlo Ersek
2020-05-21 17:53 ` Sean
2020-05-22 2:59 ` Andrew Fish
2020-05-22 5:48 ` [EXTERNAL] " Bret Barkelew
2020-05-22 17:20 ` Laszlo Ersek
2020-05-25 4:09 ` [EXTERNAL] " Andrew Fish
2020-05-25 18:10 ` Laszlo Ersek
2020-05-25 18:28 ` Andrew Fish
2020-05-26 11:17 ` Laszlo Ersek
2020-05-26 14:39 ` Samer El-Haj-Mahmoud
2020-05-26 16:13 ` Bret Barkelew
2020-05-27 1:52 ` Bret Barkelew
2020-05-27 9:27 ` Tomas Pilar (tpilar)
2020-05-27 12:12 ` Laszlo Ersek
2020-05-27 22:07 ` Rebecca Cran
2020-05-27 17:39 ` Andrew Fish
2020-05-27 17:45 ` Bret Barkelew
2020-05-28 6:57 ` Bret Barkelew [this message]
2020-05-27 18:32 ` Laszlo Ersek
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-list 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=CY4PR21MB0743B77264CD589D6F518299EF8E0@CY4PR21MB0743.namprd21.prod.outlook.com \
--to=devel@edk2.groups.io \
/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