git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 (Feb 2025, #06; Tue, 18)
Date: Thu, 20 Feb 2025 12:18:15 +0100	[thread overview]
Message-ID: <Z7cPd79kZzJkLPi3@pks.im> (raw)
In-Reply-To: <xmqqy0y2hg8l.fsf@gitster.g>

On Tue, Feb 18, 2025 at 05:31:54PM -0800, Junio C Hamano wrote:
> * ps/path-sans-the-repository (2025-02-07) 16 commits
>  - path: adjust last remaining users of `the_repository`
>  - environment: move access to "core.sharedRepository" into repo settings
>  - environment: move access to "core.hooksPath" into repo settings
>  - repo-settings: introduce function to clear struct
>  - path: drop `git_path()` in favor of `repo_git_path()`
>  - rerere: let `rerere_path()` write paths into a caller-provided buffer
>  - path: drop `git_common_path()` in favor of `repo_common_path()`
>  - worktree: return allocated string from `get_worktree_git_dir()`
>  - path: drop `git_path_buf()` in favor of `repo_git_path_replace()`
>  - path: drop `git_pathdup()` in favor of `repo_git_path()`
>  - path: drop unused `strbuf_git_path()` function
>  - path: refactor `repo_submodule_path()` family of functions
>  - submodule: refactor `submodule_to_gitdir()` to accept a repo
>  - path: refactor `repo_worktree_path()` family of functions
>  - path: refactor `repo_git_path()` family of functions
>  - path: refactor `repo_common_path()` family of functions
> 
>  The path.[ch] API takes an explicit repository parameter passed
>  throughout the callchain, instead of relying on the_repository
>  singleton instance.
>  source: <20250207-b4-pks-path-drop-the-repository-v2-0-13cad3c11b8a@pks.im>

This series has been Ack'd by both Karthik and Jialuo -- do you want me
to pull in additional reviewers to move it forward?

> * ps/build-meson-fixes-0130 (2025-01-30) 14 commits
>  - gitlab-ci: restrict maximum number of link jobs on Windows
>  - meson: consistently use custom program paths to resolve programs
>  - meson: fix overwritten `git` variable
>  - meson: prevent finding sed(1) in a loop
>  - meson: improve handling of `sane_tool_path` option
>  - meson: improve PATH handling
>  - meson: drop separate version library
>  - meson: stop linking libcurl into all executables
>  - meson: introduce `libgit_curl` dependency
>  - meson: simplify use of the common-main library
>  - meson: inline the static 'git' library
>  - meson: fix OpenSSL fallback when not explicitly required
>  - meson: fix exec path with enabled runtime prefix
>  - Merge branch 'ps/build-meson-fixes' into ps/build-meson-fixes-0130
> 
>  Assorted fixes and improvements to the build procedure based on
>  meson.
> 
>  Needs review.
>  source: <20250130-b4-pks-meson-improvements-v2-0-2f05581ffb44@pks.im>

This one has also received two reviews by Toon and Justin and it has
been cooking for quite a while, so the same question here.

Thanks!

Patrick

  reply	other threads:[~2025-02-20 11:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-19  1:31 What's cooking in git.git (Feb 2025, #06; Tue, 18) Junio C Hamano
2025-02-20 11:18 ` Patrick Steinhardt [this message]
2025-02-20 15:56   ` Junio C Hamano

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=Z7cPd79kZzJkLPi3@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 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).