* warning: ignoring unknown core.fsync component 'true'
@ 2025-07-23 3:07 Wang, Jinfeng (CN)
2025-07-23 5:27 ` Patrick Steinhardt
0 siblings, 1 reply; 3+ messages in thread
From: Wang, Jinfeng (CN) @ 2025-07-23 3:07 UTC (permalink / raw)
To: git; +Cc: jinfeng.wang.cn
Hi all,
For a specific git repo, when I clone or fetch the repo, I encounters
the warning
remote: warning: ignoring unknown core.fsync component 'true'
remote: Enumerating objects: 41, done.
remote: Total 41 (delta 0), reused 0 (delta 0), pack-reused 41
Unpacking objects: 100% (41/41), 37.51 MiB | 10.91 MiB/s, done.
But after clone the repo, I didn't see core.fsync in my .git/config. And
there isn't anything relates core.fsync.
I also tried git with different version (2.25.1 and 2.34.1) to clone the
repo, both will show this warning. What configuration causes this warning?
Regards.
Jinfeng
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: warning: ignoring unknown core.fsync component 'true'
2025-07-23 3:07 warning: ignoring unknown core.fsync component 'true' Wang, Jinfeng (CN)
@ 2025-07-23 5:27 ` Patrick Steinhardt
2025-07-24 8:08 ` Wang, Jinfeng (CN)
0 siblings, 1 reply; 3+ messages in thread
From: Patrick Steinhardt @ 2025-07-23 5:27 UTC (permalink / raw)
To: Wang, Jinfeng (CN); +Cc: git
Hi Jinfeng,
On Wed, Jul 23, 2025 at 11:07:37AM +0800, Wang, Jinfeng (CN) wrote:
> For a specific git repo, when I clone or fetch the repo, I encounters the
> warning
>
> remote: warning: ignoring unknown core.fsync component 'true'
> remote: Enumerating objects: 41, done.
> remote: Total 41 (delta 0), reused 0 (delta 0), pack-reused 41
> Unpacking objects: 100% (41/41), 37.51 MiB | 10.91 MiB/s, done.
>
> But after clone the repo, I didn't see core.fsync in my .git/config. And
> there isn't anything relates core.fsync.
The problem doesn't exist on the client-side, but rather on the remote
as indicated by the "remote: " prefix. So there's nothing you can do on
the client-side to address the problem, you'll have to reach out to the
admin of that repository and tell them that the repository uses an
invalid value for "core.fsync".
> I also tried git with different version (2.25.1 and 2.34.1) to clone the
> repo, both will show this warning. What configuration causes this warning?
It's "core.fsync" indeed, but not on your side. The config does not take
a boolean, but rather a list of components that should use fsync. I
guess the admin wanted to just fsync everything, but in that case you
don't want "core.fsync=true" but "core.fsync=all".
Patrick
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: warning: ignoring unknown core.fsync component 'true'
2025-07-23 5:27 ` Patrick Steinhardt
@ 2025-07-24 8:08 ` Wang, Jinfeng (CN)
0 siblings, 0 replies; 3+ messages in thread
From: Wang, Jinfeng (CN) @ 2025-07-24 8:08 UTC (permalink / raw)
To: Patrick Steinhardt; +Cc: git
Hi Patrick,
Thanks.
On 7/23/2025 1:27 PM, Patrick Steinhardt wrote:
> CAUTION: This email comes from a non Wind River email account!
> Do not click links or open attachments unless you recognize the sender and know the content is safe.
>
> Hi Jinfeng,
>
> On Wed, Jul 23, 2025 at 11:07:37AM +0800, Wang, Jinfeng (CN) wrote:
>> For a specific git repo, when I clone or fetch the repo, I encounters the
>> warning
>>
>> remote: warning: ignoring unknown core.fsync component 'true'
>> remote: Enumerating objects: 41, done.
>> remote: Total 41 (delta 0), reused 0 (delta 0), pack-reused 41
>> Unpacking objects: 100% (41/41), 37.51 MiB | 10.91 MiB/s, done.
>>
>> But after clone the repo, I didn't see core.fsync in my .git/config. And
>> there isn't anything relates core.fsync.
> The problem doesn't exist on the client-side, but rather on the remote
> as indicated by the "remote: " prefix. So there's nothing you can do on
> the client-side to address the problem, you'll have to reach out to the
> admin of that repository and tell them that the repository uses an
> invalid value for "core.fsync".
>
>> I also tried git with different version (2.25.1 and 2.34.1) to clone the
>> repo, both will show this warning. What configuration causes this warning?
> It's "core.fsync" indeed, but not on your side. The config does not take
> a boolean, but rather a list of components that should use fsync. I
> guess the admin wanted to just fsync everything, but in that case you
> don't want "core.fsync=true" but "core.fsync=all".
>
> Patrick
Regards,
Jinfeng
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2025-07-24 8:08 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2025-07-23 3:07 warning: ignoring unknown core.fsync component 'true' Wang, Jinfeng (CN)
2025-07-23 5:27 ` Patrick Steinhardt
2025-07-24 8:08 ` Wang, Jinfeng (CN)
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 NNTP newsgroup(s).