Re: [PATCH] fsmonitor: long status advice adapted to the fsmonitor use case

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

Subject: Re: [PATCH] fsmonitor: long status advice adapted to the fsmonitor use case
From: Rudy Rigot <rudy.rigot@xxxxxxxxx>
Date: Sat, 15 Oct 2022 08:08:45 -0500
Cc: git@xxxxxxxxxxxxxxx
In-reply-to: <pull.1384.git.1665839050813.gitgitgadget@gmail.com>
References: <pull.1384.git.1665839050813.gitgitgadget@gmail.com>

> I considered just suppressing that piece of advice entirely for
repositories with fsmonitor disabled

Sorry, I just noticed that I misspoke here. I meant repositories with
fsmonitor *enabled*, of course.

References:
- [PATCH] fsmonitor: long status advice adapted to the fsmonitor use case
  - From: Rudy Rigot via GitGitGadget

Prev by Date: [PATCH] fsmonitor: long status advice adapted to the fsmonitor use case
Next by Date: Re: [PATCH] sparse-checkout.txt: new document with sparse-checkout directions
Previous by thread: [PATCH] fsmonitor: long status advice adapted to the fsmonitor use case
Next by thread: Re: [PATCH] fsmonitor: long status advice adapted to the fsmonitor use case
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