From: Junio C Hamano <gitster@pobox.com>
To: karthik nayak <karthik.188@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Dec 2024, #05; Thu, 12)
Date: Fri, 13 Dec 2024 23:33:51 +0900 [thread overview]
Message-ID: <xmqq7c83ejow.fsf@gitster.g> (raw)
In-Reply-To: <CAOLa=ZQmDyy1yajNzASUkRZeizroyCXcgsRK+fOtstatg5r=2A@mail.gmail.com> (karthik nayak's message of "Thu, 12 Dec 2024 09:27:17 -0500")
karthik nayak <karthik.188@gmail.com> writes:
> Junio C Hamano <gitster@pobox.com> writes:
>
> [snip]
>
>> * kn/reftable-writer-log-write-verify (2024-12-07) 1 commit
>> - reftable/writer: ensure valid range for log's update_index
>>
>> source: <20241206-424-reftable-writer-add-check-for-limits-v2-1-82ca350b10be@gmail.com>
>>
>
> Hey Junio, this was reviewed by Patrick and Toon. I see this was added
> to 'seen'. Is it also scheduled for 'next'?
If it does not say "Will do X", it is not scheduled for that.
This applies to everybody, not specifically to you, but when you see
an empty entry like the above in the "What's cooking" report, three
things you can do are:
(1) offer a few lines of topic summary
(2) point at the review message(s)
(3) suggest for updated status with rationale (e.g. "let's move
this to 'next' by day X, as this and that reviews at URL1 and
URL2 seem to indicate that we have a concensus that it is ready".
Patrick's comments were on the previous one, IIRC, but I do see Toon
commented on the latest round.
Thanks.
next prev parent reply other threads:[~2024-12-13 14:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-12 12:31 What's cooking in git.git (Dec 2024, #05; Thu, 12) Junio C Hamano
2024-12-12 14:27 ` karthik nayak
2024-12-13 14:33 ` Junio C Hamano [this message]
2024-12-13 17:28 ` karthik nayak
2024-12-13 14:40 ` Christian Couder
2024-12-13 14:48 ` Junio C Hamano
2024-12-16 8:11 ` Patrick Steinhardt
2024-12-16 16:26 ` 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=xmqq7c83ejow.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=karthik.188@gmail.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).