From: "Hans-Bernhard Bröker" <HBBroeker@t-online.de>
To: cygwin@cygwin.com
Subject: Re: CRITICAL ls MEMORY LEAK
Date: Mon, 22 Feb 2021 22:50:24 +0100 [thread overview]
Message-ID: <e4540cda-2874-71e4-fc56-9a53a7d8e5ee@t-online.de> (raw)
In-Reply-To: <306dd40d-666d-4a27-0a2c-dc03053d2f8c@SystematicSw.ab.ca>
Am 22.02.2021 um 21:30 schrieb Brian Inglis:
> I've often wondered if the heavy activity is due to Windows' defaults to
> writing files with F+RX perms which triggers executable virus scans?
That could only be the case if Windows actually had an 'x' permission bit.
next prev parent reply other threads:[~2021-02-22 21:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-21 15:18 neal.garrett
2021-02-21 18:05 ` Brian Inglis
2021-02-22 20:12 ` Doug Henderson
2021-02-22 20:30 ` Brian Inglis
2021-02-22 21:50 ` Hans-Bernhard Bröker [this message]
2021-02-22 23:47 ` Brian Inglis
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=e4540cda-2874-71e4-fc56-9a53a7d8e5ee@t-online.de \
--to=hbbroeker@t-online.de \
--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).