From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Cc: Patrick Steinhardt <ps@pks.im>,
Abraham Samuel Adekunle <abrahamadekunle50@gmail.com>
Subject: Re: What's cooking in git.git (Feb 2026, #04)
Date: Wed, 11 Feb 2026 12:46:42 -0800 [thread overview]
Message-ID: <xmqqo6lvrost.fsf@gitster.g> (raw)
In-Reply-To: <xmqq5x84xms1.fsf@gitster.g> (Junio C. Hamano's message of "Tue, 10 Feb 2026 14:21:34 -0800")
Junio C Hamano <gitster@pobox.com> writes:
Sorry, but I need to fix a few obvious "oops, that's embarrassing"
mistakes.
> * aa/add-p-no-auto-advance (2026-02-06) 3 commits
> - add-patch: Allow proper 'git apply' when using the --rework-with-file flag
> - add-patch: Allow interfile navigation when selecting hunks
> - interactive -p: add new `--rework-with-file` flag to interactive machinery
>
> "git add -p" learned a new mode that allows the user to revisit a
> file that was already dealt with.
>
> Expecting a gitk update.
> source: <cover.1770390576.git.abrahamadekunle50@gmail.com>
No, this is not about "gitk" at all. It is expecting a hopefully
small and final reroll.
> * ps/meson-gitk-git-gui (2026-02-04) 1 commit
> - meson: wire up gitk and git-gui
>
> Plumb gitk/git-gui build and install procedure in meson based
> builds.
>
> Expecting a reroll.
> source: <20260204-b4-pks-meson-tcl-tk-v2-1-5bc3ccf3a8ce@pks.im>
This is the one that waits updated "gitk".
Thanks.
next prev parent reply other threads:[~2026-02-11 20:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-10 22:21 What's cooking in git.git (Feb 2026, #04) Junio C Hamano
2026-02-11 14:23 ` ps/object-info-bits-cleanup (was: What's cooking in git.git (Feb 2026, #04)) Patrick Steinhardt
2026-02-11 17:35 ` ps/object-info-bits-cleanup Junio C Hamano
2026-02-12 6:34 ` ps/object-info-bits-cleanup Patrick Steinhardt
2026-02-11 20:46 ` Junio C Hamano [this message]
2026-02-12 10:26 ` What's cooking in git.git (Feb 2026, #04) Samuel Abraham
2026-02-12 15:56 ` Phillip Wood
2026-02-12 16:38 ` Junio C Hamano
2026-02-13 16:06 ` Phillip Wood
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=xmqqo6lvrost.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=abrahamadekunle50@gmail.com \
--cc=git@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.