From: "Wang, Jinfeng (CN)" <jinfeng.wang.cn@windriver.com>
To: git@vger.kernel.org
Cc: jinfeng.wang.cn@windriver.com
Subject: warning: ignoring unknown core.fsync component 'true'
Date: Wed, 23 Jul 2025 11:07:37 +0800 [thread overview]
Message-ID: <209ecbf7-0d53-4674-bb7b-3ca084edb761@windriver.com> (raw)
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
next reply other threads:[~2025-07-23 3:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-23 3:07 Wang, Jinfeng (CN) [this message]
2025-07-23 5:27 ` warning: ignoring unknown core.fsync component 'true' Patrick Steinhardt
2025-07-24 8:08 ` Wang, Jinfeng (CN)
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=209ecbf7-0d53-4674-bb7b-3ca084edb761@windriver.com \
--to=jinfeng.wang.cn@windriver.com \
--cc=git@vger.kernel.org \
/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 NNTP newsgroup(s).