git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Toon Claes <toon@iotcl.com>
Cc: Patrick Steinhardt <ps@pks.im>,  git@vger.kernel.org
Subject: Re: What's cooking in git.git (Jan 2025, #06; Wed, 22)
Date: Fri, 24 Jan 2025 09:05:23 -0800	[thread overview]
Message-ID: <xmqqed0s16ss.fsf@gitster.g> (raw)
In-Reply-To: <874j1o5q2c.fsf@iotcl.com> (Toon Claes's message of "Fri, 24 Jan 2025 13:55:39 +0100")

Toon Claes <toon@iotcl.com> writes:

> Patrick Steinhardt <ps@pks.im> writes:
>
>> On Wed, Jan 22, 2025 at 02:48:43PM -0800, Junio C Hamano wrote:
>>> * ps/build-meson-fixes (2025-01-22) 12 commits
>>>  - ci: wire up Visual Studio build with Meson
>>>  ...
>>>  Will merge to 'next'?
>>>  source: <20250122-b4-pks-meson-additions-v3-0-5a51eb5d3dcd@pks.im>
>>
>> Ready from my perspective.
>
> I can't really vouch for the last commit about Visual Studio, but the
> other commits are ready for me as well.

Thanks.

  reply	other threads:[~2025-01-24 17:05 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-22 22:48 What's cooking in git.git (Jan 2025, #06; Wed, 22) Junio C Hamano
2025-01-23  0:36 ` Jeff King
2025-01-23  1:52   ` Junio C Hamano
2025-01-31 23:34     ` Jeff King
2025-01-31 23:39       ` Jeff King
2025-01-31 23:49       ` Junio C Hamano
2025-02-01  2:29         ` Jeff King
2025-02-02 23:39           ` Junio C Hamano
2025-02-03 13:51             ` Junio C Hamano
2025-02-04  2:35               ` Jeff King
2025-02-02 18:09       ` D. Ben Knoble
2025-02-02 23:33       ` Junio C Hamano
2025-02-03 15:33         ` Jeff King
2025-01-23  0:38 ` Eric Sunshine
2025-01-23  1:53   ` Junio C Hamano
2025-01-23 17:36 ` Taylor Blau
2025-01-24  6:07 ` Patrick Steinhardt
2025-01-24 12:55   ` Toon Claes
2025-01-24 17:05     ` Junio C Hamano [this message]
2025-01-24 16:02   ` 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=xmqqed0s16ss.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=ps@pks.im \
    --cc=toon@iotcl.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).