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 (Nov 2025, #02; Thu, 6)
Date: Fri, 7 Nov 2025 07:50:03 +0100	[thread overview]
Message-ID: <aQ2WkAmkEep4AWqT@pks.im> (raw)
In-Reply-To: <xmqqms4zhxp4.fsf@gitster.g>

On Thu, Nov 06, 2025 at 09:34:31AM -0800, Junio C Hamano wrote:
> * dk/make-git-contacts-executable (2025-11-04) 1 commit
>  - perl: also mark git-contacts executable
> 
>  Building "git contacts" script (in contrib/) leaves the resulting
>  file unexecutable, which has been corrected.
> 
>  Will merge to 'next'?
>  source: <7fbb341e8f05fcde3a1543e3bb4e5a3ec1101692.1762280097.git.ben.knoble+github@gmail.com>

Yup. I see you fixed up the grammar issue in the commit message, so I'm
good with this being merged.

> * dk/meson-html-dir (2025-11-04) 1 commit
>  - meson: make GIT_HTML_PATH configurable
> 
>  The build procedure based on meson learned to allow builders to
>  specify the directory to install HTML documents.
> 
>  Will merge to 'next'?
>  source: <385992f6020703558f0ba75a1be6c4f9dae08b83.1762264709.git.ben.knoble+github@gmail.com>

Likewise, you've fixed the ordering of the Meson options, which was my
only nit. So this looks good to me, as well.

> * ps/object-source-loose (2025-11-02) 13 commits
>  - object-file: refactor writing objects via a stream
>  - object-file: rename `write_object_file()`
>  - object-file: refactor freshening of objects
>  - object-file: rename `has_loose_object()`
>  - object-file: read objects via the loose object source
>  - object-file: move loose object map into loose source
>  - object-file: hide internals when we need to reprepare loose sources
>  - object-file: move loose object cache into loose source
>  - object-file: introduce `struct odb_source_loose`
>  - object-file: move `fetch_if_missing`
>  - odb: adjust naming to free object sources
>  - odb: introduce `odb_source_new()`
>  - odb: fix subtle logic to check whether an alternate is usable
> 
>  A part of code paths that deals with loose objects has been cleaned
>  up.
> 
>  Will merge to 'next'?
>  source: <20251103-b4-pks-odb-loose-backend-v3-0-6a61ea977393@pks.im>

Yup, I think v3 is ready to be merged.

> * ps/rust-cbindgen (2025-10-24) 6 commits
>  . rust: generate bindings via cbindgen
>  . meson: rename Rust library target
>  . ci: use Debian instead of deprecated i386/ubuntu
>  . gitlab-ci: backfill missing Linux jobs
>  . gitlab-ci: reorder Linux job matrix to match GitHub's order
>  . Merge branch 'ps/ci-rust' into ps/rust-cbindgen
> 
>  Introduce cbindgen in the build framework to help interfacing with
>  Rust.
> 
>  More discussion?
>  cf. <20251024-b4-pks-rust-cbindgen-v2-0-4b4bd4f18490@pks.im>
>  source: <20251024-b4-pks-rust-cbindgen-v2-0-4b4bd4f18490@pks.im>

Yeah. I'll probably have to introduce workspaces as Ezekiel explained,
but I didn't have the time recently to handle this yet.

Thanks!

Patrick

  reply	other threads:[~2025-11-07  6:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-06 17:34 What's cooking in git.git (Nov 2025, #02; Thu, 6) Junio C Hamano
2025-11-07  6:50 ` Patrick Steinhardt [this message]
2025-11-07 11:25 ` ps/rust-cbindgen (was: What's cooking in git.git (Nov 2025, #02; Thu, 6)) 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=aQ2WkAmkEep4AWqT@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).