Git development
 help / color / mirror / Atom feed
From: Ben Knoble <ben.knoble@gmail.com>
To: Ramkumar Ramachandra <r@artagnon.com>
Cc: "brian m. carlson" <sandals@crustytoothpaste.net>,
	Git List <git@vger.kernel.org>
Subject: Re: User report on git 2.55.0
Date: Fri, 4 Sep 2026 19:20:36 -0400	[thread overview]
Message-ID: <A918E4C6-AF5B-47A8-B2FF-69E87F6118D1@gmail.com> (raw)
In-Reply-To: <14ec96fa-897c-4bf6-a2e9-cd0c6e9b4474@app.fastmail.com>


> Le 4 sept. 2026 à 19:13, Ramkumar Ramachandra <r@artagnon.com> a écrit :
> 
> Ramkumar Ramachandra wrote:
>> brian m. carlson wrote:
>>> Do you maybe have some sort of security software running on your Mac?
>> 
>> I think it's clean, but it's still a possibility that the workplace
>> installed something recently: I don't see any other strange symptoms
>> with any other software though, and everything seems to working
>> reliably? Perhaps the most common task: I run llvm tests over 30 times
>> a day on different changes, and it never reports any spurious failures?
>> I will nevertheless ask the IT team at my workplace if something that I
>> can't see was installed. I don't use my personal laptop for llvm work,
>> so doing that comparison is not possible.
> 
> I found the malware: it's Crowdstrike Falcon x(

Hear hear. I haven’t observed issues with Git (based on next, I believe) I compile and install to $HOME at work, but I think we also use CrowdStrike Falcon. I’ll keep my eye out, but the scale of repos I deal with on that ‘puter doesn’t come close. 

  reply	other threads:[~2026-09-04 23:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-04 18:05 User report on git 2.55.0 Ramkumar Ramachandra
2026-09-04 19:22 ` brian m. carlson
2026-09-04 20:32   ` Ramkumar Ramachandra
2026-09-04 23:10     ` Ramkumar Ramachandra
2026-09-04 23:20       ` Ben Knoble [this message]
2026-09-04 23:42         ` Ramkumar Ramachandra

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=A918E4C6-AF5B-47A8-B2FF-69E87F6118D1@gmail.com \
    --to=ben.knoble@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=r@artagnon.com \
    --cc=sandals@crustytoothpaste.net \
    /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