From: "KAVALAGIOS Panagiotis (EEAS-EXT)" <Panagiotis.KAVALAGIOS@ext.eeas.europa.eu>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: RE: Git shows nothing in cmd.exe
Date: Wed, 11 Nov 2020 09:28:19 +0000 [thread overview]
Message-ID: <842e4318f3954a2980588059e7e431a7@BELBRU-EXMP101.eeas.europa.eu> (raw)
In-Reply-To: <09a3fd0d-81ba-11c0-1e85-b3578f39e9f6@SystematicSw.ab.ca>
> -----Original Message-----
> From: Cygwin <cygwin-bounces@cygwin.com> On Behalf Of Brian Inglis
> Sent: 10 November 2020 17:13
> Subject: Re: Git shows nothing in cmd.exe
>
> Gnuwin32 *latest* package updates seem to be 10 years ago, some nearly
> 20.
> Suggest deleting those and using current *mingw64*/msys Windows tools
> instead as they are maintained with recent security fixes.
> You should also be careful with PATHs using different toolchains: switch them
> completely, or layer them carefully, to avoid these issues.
You are absolutely right! This is what we are going to do. We will remove that package from our machines.
PATH is indeed yet another headache. We are trying to prepend or append entries to set correctly the behaviour by overriding other applications to no avail. Issues can still be faced.
Panos
next prev parent reply other threads:[~2020-11-11 9:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-10 10:35 KAVALAGIOS Panagiotis (EEAS-EXT)
2020-11-10 12:03 ` Adam Dinwoodie
[not found] ` <72f4f32d00e44071afbaa74b6b77ebad@BELBRU-EXMP101.eeas.europa.eu>
2020-11-10 12:56 ` Adam Dinwoodie
2020-11-10 13:35 ` KAVALAGIOS Panagiotis (EEAS-EXT)
2020-11-10 16:13 ` Brian Inglis
2020-11-11 9:28 ` KAVALAGIOS Panagiotis (EEAS-EXT) [this message]
2020-11-11 10:43 ` Andrey Repin
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=842e4318f3954a2980588059e7e431a7@BELBRU-EXMP101.eeas.europa.eu \
--to=panagiotis.kavalagios@ext.eeas.europa.eu \
--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).