RE: [BUG REPORT] fsmonitor and core.untrackedCache combination causes inaccurate git status

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: RE: [BUG REPORT] fsmonitor and core.untrackedCache combination causes inaccurate git status
From: Joni Lameter <jlameter@xxxxxxxx>
Date: Mon, 24 Jun 2024 17:43:45 +0000
Accept-language: en-US
In-reply-to: <DM6PR17MB215602138249E744ECFE4185A6E62@DM6PR17MB2156.namprd17.prod.outlook.com>
References: <DM6PR17MB215602138249E744ECFE4185A6E62@DM6PR17MB2156.namprd17.prod.outlook.com>
Thread-index: AdqiJ8SyNgb1asgGRQOGVfbRsdLCvAkNfU3Q
Thread-topic: [BUG REPORT] fsmonitor and core.untrackedCache combination causes inaccurate git status

I haven't heard back about this bug report. Is there any additional 
info that would be helpful here? Should I have reported this 
somewhere else?

References:
- [BUG REPORT] fsmonitor and core.untrackedCache combination causes inaccurate git status
  - From: Joni Lameter

Prev by Date: Re: [PATCH] describe: refresh the index when 'broken' flag is used
Next by Date: Re: Thoughts about the -m option of cherry-pick and revert
Previous by thread: [BUG REPORT] fsmonitor and core.untrackedCache combination causes inaccurate git status
Next by thread: [PATCH] SubmittingPatches: advertise git-manpages-l10n project a bit
Index(es):
- Date
- Thread

[Index of Archives] [Linux Kernel Development] [Gcc Help] [IETF Annouce] [DCCP] [Netdev] [Networking] [Security] [V4L] [Bugtraq] [Yosemite] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Linux SCSI] [Fedora Users]

Powered by Linux