From: Patrick Steinhardt <ps@pks.im>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Oct 2026, #05)
Date: Wed, 14 Oct 2026 09:08:52 +0200 [thread overview]
Message-ID: <as8qhADRcxyQ_rMn@pks.im> (raw)
In-Reply-To: <xmqq33u9uprk.fsf@gitster.g>
On Tue, Oct 13, 2026 at 04:47:27PM -0700, Junio C Hamano wrote:
> * ps/setup-enforce-repo-passed-to-create-repository-has-no-state (2026-09-28) 7 commits
> - setup: enforce that passed-in repo does not carry relevant state
> - repository: adapt `repo_clear()` to fully reset the repository
> - builtin/clone: don't apply "core.sharedRepository" to leading dirs
> - builtin/init: move handling of "core.sharedRepository" into "setup.c"
> - builtin/init: refactor messy creation of leading directories
> - path: introduce `safe_create_leading_directories_no_share_const()`
> - path: drop useless `safe_create_leading_directories_1()`
> - Merge branch 'ps/odb-alternates-at-creation' into ps/setup-enforce-repo-passed-to-create-repository-has-no-state
>
> The repository initialization sequence has been refactored to treat
> the repository object passed to create_repository() purely as an
> out-parameter.
>
> Waiting for response.
> cf. <CAOLa=ZSX0e25wK5qQwznXN9rVM+WHn8631pkTEN9Zm-BrXfEsg@mail.gmail.com>
> cf. <xmqqtsn9mkog.fsf@gitster.g>
> source: <20260928-pks-create-repository-stateless-v2-0-a03612f703fa@pks.im>
I think this one is still stale, see [1] :)
Patrick
[1]: <xmqqjyo016z4.fsf@gitster.g>
prev parent reply other threads:[~2026-10-14 7:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-13 23:47 What's cooking in git.git (Oct 2026, #05) Junio C Hamano
2026-10-14 0:25 ` Ben Knoble
2026-10-14 7:08 ` Patrick Steinhardt [this message]
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=as8qhADRcxyQ_rMn@pks.im \
--to=ps@pks.im \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.