From: Junio C Hamano <gitster@pobox.com>
To: Johannes Sixt <j6t@kdbg.org>
Cc: Jeff King <peff@peff.net>,
git@vger.kernel.org, Patrick Steinhardt <ps@pks.im>
Subject: Re: [PATCH v2] meson: wire up gitk and git-gui
Date: Wed, 11 Feb 2026 14:56:57 -0800 [thread overview]
Message-ID: <xmqqh5rmrirq.fsf@gitster.g> (raw)
In-Reply-To: <5975950d-873c-4bc9-90b6-e062021ab5de@kdbg.org> (Johannes Sixt's message of "Wed, 11 Feb 2026 23:41:33 +0100")
Johannes Sixt <j6t@kdbg.org> writes:
> Am 11.02.26 um 22:05 schrieb Junio C Hamano:
>> Patrick Steinhardt <ps@pks.im> writes:
>>> On Thu, Feb 05, 2026 at 12:55:04PM +0100, Patrick Steinhardt wrote:
>>> The fix has been merged upstream. I've created [1] to verify that the CI
>>> now succeeds.
>>
>> Hannes, I see that in your tree
>>
>> https://github.com/j6t/gitk/commit/ddae547e3775638c238c11f30120f1e7e763fba8
>>
>> has Patrick's fix. Is it a good time for me to pull from you, or do
>> you want/need to finish any housekeeping tasks like tagging before I
>> do?
>>
>> This will hopefully help us unblock one of in-flight topics.
> Please feel free to pull this commit (it's today's master).
>
> I was pondering whether I want to include more topics in the next pull
> request, but I didn't find the time to make up my mind. So, let's take
> the fast route for now.
>
> -- Hannes
Thanks!
prev parent reply other threads:[~2026-02-11 22:57 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-19 8:18 [PATCH 0/3] meson: wire up gitk and git-gui Patrick Steinhardt
2025-08-19 8:18 ` [PATCH 1/3] git-gui: move into "subprojects/" Patrick Steinhardt
2025-08-19 9:36 ` Karthik Nayak
2025-08-19 8:18 ` [PATCH 2/3] gitk: " Patrick Steinhardt
2025-08-20 5:49 ` [PATCH] doc/gitk: update reference to the external project Johannes Sixt
2025-08-20 6:16 ` [PATCH v2] " Johannes Sixt
2025-08-20 15:34 ` Junio C Hamano
2025-08-19 8:18 ` [PATCH 3/3] meson: wire up gitk and git-gui Patrick Steinhardt
2025-08-19 9:40 ` Karthik Nayak
2025-08-24 17:25 ` Patrick Steinhardt
2025-08-19 15:49 ` [PATCH 0/3] " Junio C Hamano
2025-08-24 17:25 ` Patrick Steinhardt
2025-08-26 0:40 ` Junio C Hamano
2025-09-02 13:00 ` Patrick Steinhardt
2025-08-19 22:25 ` Ramsay Jones
2025-08-24 17:25 ` Patrick Steinhardt
2026-02-04 8:38 ` [PATCH v2] " Patrick Steinhardt
2026-02-04 10:00 ` Karthik Nayak
2026-02-04 11:56 ` Patrick Steinhardt
2026-02-04 17:53 ` Junio C Hamano
2026-02-05 6:58 ` Patrick Steinhardt
2026-02-05 9:37 ` Jeff King
2026-02-05 11:55 ` Patrick Steinhardt
2026-02-06 15:39 ` Patrick Steinhardt
2026-02-06 22:23 ` Junio C Hamano
2026-02-09 8:32 ` Patrick Steinhardt
2026-02-11 21:05 ` Junio C Hamano
2026-02-11 22:41 ` Johannes Sixt
2026-02-11 22:56 ` Junio C Hamano [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=xmqqh5rmrirq.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=j6t@kdbg.org \
--cc=peff@peff.net \
--cc=ps@pks.im \
/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