git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Patrick Steinhardt <ps@pks.im>
To: "Wang, Jinfeng (CN)" <jinfeng.wang.cn@windriver.com>
Cc: git@vger.kernel.org
Subject: Re: warning: ignoring unknown core.fsync component 'true'
Date: Wed, 23 Jul 2025 07:27:59 +0200	[thread overview]
Message-ID: <aIBy3xH2eZsCZYiY@pks.im> (raw)
In-Reply-To: <209ecbf7-0d53-4674-bb7b-3ca084edb761@windriver.com>

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

  reply	other threads:[~2025-07-23  5:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-23  3:07 warning: ignoring unknown core.fsync component 'true' Wang, Jinfeng (CN)
2025-07-23  5:27 ` Patrick Steinhardt [this message]
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=aIBy3xH2eZsCZYiY@pks.im \
    --to=ps@pks.im \
    --cc=git@vger.kernel.org \
    --cc=jinfeng.wang.cn@windriver.com \
    /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).