From: Junio C Hamano <gitster@pobox.com>
To: "Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Sep 2025, #03; Mon, 8)
Date: Wed, 10 Sep 2025 14:37:32 -0700 [thread overview]
Message-ID: <xmqq8qimq99f.fsf@gitster.g> (raw)
In-Reply-To: <226976fa-2805-485c-b01e-138e06f9c7bb@app.fastmail.com> (Kristoffer Haugsbakk's message of "Wed, 10 Sep 2025 09:42:59 +0200")
"Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail.com> writes:
> On Tue, Sep 9, 2025, at 03:37, Junio C Hamano wrote:
>> * kh/doc-fast-import-markup-fix (2025-09-08) 1 commit
>> - doc: fast-import: replace literal block with paragraph
>>
>> Doc mark-up fix.
>>
>> Will merge to 'next'.
>> source:
>> <09aaad696895c18c6d4dda7d6a2f4b77f84f39ba.1757363213.git.code@khaugsbakk.name>
>
> Nit: The ref still points to v1. Although v2 just has the Ack:
>
> <724b975078daf11e17f26472c0da5638a5d1ca86.1757366352.git.code@khaugsbakk.name>
It is not just the ref. The updated version has not been picked up
at all. Thanks for letting me know.
Is it just Peff's Ack, or any other changes added to the patch?
Thanks.
next prev parent reply other threads:[~2025-09-10 21:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-09 1:37 What's cooking in git.git (Sep 2025, #03; Mon, 8) Junio C Hamano
2025-09-09 6:58 ` Elijah Newren
2025-09-09 19:35 ` Derrick Stolee
2025-09-09 21:20 ` Junio C Hamano
2025-09-10 7:42 ` Kristoffer Haugsbakk
2025-09-10 21:37 ` Junio C Hamano [this message]
2025-09-10 21:44 ` Kristoffer Haugsbakk
2025-09-10 15:32 ` Phillip Wood
2025-09-10 21:38 ` Junio C Hamano
2025-09-10 15:54 ` Jeff King
2025-09-10 21:42 ` 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=xmqq8qimq99f.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=kristofferhaugsbakk@fastmail.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).