From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: Kevin Puetz <PuetzKevinA@johndeere.com>,
"brian m. carlson" <sandals@crustytoothpaste.net>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: [Bug] git fetch --dry-run --filter makes changes to .git/config
Date: Thu, 18 Sep 2025 13:46:17 -0700 [thread overview]
Message-ID: <xmqqecs37ali.fsf@gitster.g> (raw)
In-Reply-To: <20250918203916.GA1199728@coredump.intra.peff.net> (Jeff King's message of "Thu, 18 Sep 2025 16:39:16 -0400")
Jeff King <peff@peff.net> writes:
> ... It is unfortunate that doing so updates the repo
> config, though. That may show a mismatch in how the promisor information
> is stored (it is really a property of the packfile in the object
> directory, but the config mechanism stores it in the main repo). But it
> is probably not worth trying to revisit at this point. It is only when
> you start to play weird games like "this repo's object directory is not
> $GIT_DIR/objects" that you run into these distinctions.
Hmph, but watching from the sidelines Patrick's topics that revolve
around (re)defining the boundary and relationship among repository,
object store, and on-disk packfiles with a more clearly defined
abstractions like object_source, I am hoping that we somehow can
find a good place to move this information out of the per-repo
configuration to somewhere close to individual packs. I dunno.
next prev parent reply other threads:[~2025-09-18 20:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-17 14:44 [Bug] git fetch --dry-run --filter makes changes to .git/config Kevin Puetz
2025-09-17 21:21 ` brian m. carlson
2025-09-17 23:23 ` Kevin Puetz
2025-09-18 19:20 ` Jeff King
2025-09-18 20:28 ` Junio C Hamano
2025-09-18 20:39 ` Jeff King
2025-09-18 20:46 ` Junio C Hamano [this message]
2025-09-18 21:55 ` Kevin Puetz
2025-09-18 22:21 ` rsbecker
2025-09-19 15:31 ` Kevin Puetz
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=xmqqecs37ali.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=PuetzKevinA@johndeere.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--cc=sandals@crustytoothpaste.net \
/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).