From: Junio C Hamano <gitster@pobox.com>
To: "René Scharfe" <l.s.r@web.de>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 0/5] tempfile: stop using the_repository
Date: Tue, 14 Jul 2026 13:45:02 -0700 [thread overview]
Message-ID: <xmqq8q7ds3ld.fsf@gitster.g> (raw)
In-Reply-To: <20260714175956.54601-1-l.s.r@web.de> ("René Scharfe"'s message of "Tue, 14 Jul 2026 19:59:51 +0200")
René Scharfe <l.s.r@web.de> writes:
> create_tempfile_mode() and create_tempfile() use the_repository
> internally to call adjust_shared_perm(). Expose that dependency and
> push it out to their callers.
>
> Patch 5 is a bonus; it converts lockfile users that already work with
> other repositories.
>
> tempfile: add repo_create_tempfile{,_mode}()
> refs/packed: use repo_create_tempfile()
> lockfile: add repo_hold_lock_file_for_update{,_timeout}{,_mode}()
> tempfile: stop using the_repository
> use repo_hold_lock_file_for_update{,_mode,_timeout}() with custom repos
Will queue. If I have a chance I may revisit the topic a bit
deeper, but nothing stood out as glaringly wrong to my cursory
reading so far.
Thanks.
>
> apply.c | 10 ++++++----
> builtin/difftool.c | 2 +-
> builtin/gc.c | 2 +-
> builtin/history.c | 2 +-
> builtin/sparse-checkout.c | 3 ++-
> bundle.c | 4 ++--
> commit-graph.c | 9 +++++----
> config.c | 4 ++--
> lockfile.c | 30 ++++++++++++++++++++++--------
> lockfile.h | 31 +++++++++++++++++++++++++++++++
> loose.c | 6 ++++--
> midx-write.c | 7 ++++---
> odb/source-files.c | 3 ++-
> refs/files-backend.c | 10 ++++++----
> refs/packed-backend.c | 9 ++++-----
> refs/packed-backend.h | 2 +-
> repack-midx.c | 3 ++-
> repository.c | 2 +-
> rerere.c | 6 +++---
> tempfile.c | 7 +++----
> tempfile.h | 10 +++++++---
> 21 files changed, 110 insertions(+), 52 deletions(-)
next prev parent reply other threads:[~2026-07-14 20:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-14 17:59 [PATCH 0/5] tempfile: stop using the_repository René Scharfe
2026-07-14 17:59 ` [PATCH 1/5] tempfile: add repo_create_tempfile{,_mode}() René Scharfe
2026-07-15 9:52 ` Patrick Steinhardt
2026-07-15 11:25 ` René Scharfe
2026-07-14 17:59 ` [PATCH 2/5] refs/packed: use repo_create_tempfile() René Scharfe
2026-07-14 17:59 ` [PATCH 3/5] lockfile: add repo_hold_lock_file_for_update{,_timeout}{,_mode}() René Scharfe
2026-07-14 17:59 ` [PATCH 4/5] tempfile: stop using the_repository René Scharfe
2026-07-15 9:52 ` Patrick Steinhardt
2026-07-14 17:59 ` [PATCH 5/5] use repo_hold_lock_file_for_update{,_mode,_timeout}() with custom repos René Scharfe
2026-07-15 9:52 ` Patrick Steinhardt
2026-07-14 20:45 ` Junio C Hamano [this message]
2026-07-15 9:51 ` [PATCH 0/5] tempfile: stop using the_repository Patrick Steinhardt
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=xmqq8q7ds3ld.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=l.s.r@web.de \
/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