Timeline for Command failed git update-git-for-windows
Current License: CC BY-SA 4.0
13 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 20, 2024 at 5:38 | answer | added | Birudeo Garande | timeline score: -1 | |
| Apr 16, 2024 at 17:06 | answer | added | Aurisgo | timeline score: -1 | |
| Dec 28, 2023 at 5:02 | answer | added | Real Uniquee | timeline score: 0 | |
| Oct 18, 2023 at 8:47 | answer | added | Daniel Calliess | timeline score: 0 | |
| Jun 12, 2023 at 6:45 | answer | added | Baris KAHRAMAN | timeline score: 1 | |
| Mar 15, 2023 at 12:27 | answer | added | mxmlc | timeline score: 5 | |
| Dec 14, 2022 at 13:00 | answer | added | slavong | timeline score: 15 | |
| Jun 14, 2022 at 14:11 | answer | added | fikusir | timeline score: 0 | |
| Jan 6, 2021 at 20:18 | answer | added | Carlos Pimentel | timeline score: 37 | |
| Nov 5, 2020 at 19:05 | answer | added | HamiltonPharmD | timeline score: 5 | |
| Oct 28, 2020 at 17:57 | comment | added | thdoan | Are you executing this from behind a corporate firewall by any chance? That was the root cause for me. | |
| Feb 29, 2020 at 6:31 | comment | added | knittl |
Not an answer (and a potential security risk!): you could create a ~/.curlrc file with a line containing insecure. This will disable TLS verification for all curl invocations.
|
|
| Feb 26, 2020 at 18:37 | history | asked | A. G. Araujo | CC BY-SA 4.0 |