From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS3215 2.6.0.0/16 X-Spam-Status: No, score=-3.4 required=3.0 tests=AWL,BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE, URIBL_CSS,URIBL_CSS_A shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from out1.vger.email (out1.vger.email [IPv6:2620:137:e000::1:20]) by dcvr.yhbt.net (Postfix) with ESMTP id C21091F670 for ; Mon, 7 Mar 2022 18:15:36 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S240088AbiCGSQ1 (ORCPT ); Mon, 7 Mar 2022 13:16:27 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:59904 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S235031AbiCGSQY (ORCPT ); Mon, 7 Mar 2022 13:16:24 -0500 Received: from pb-smtp20.pobox.com (pb-smtp20.pobox.com [173.228.157.52]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id C1D8832EF9 for ; Mon, 7 Mar 2022 10:15:29 -0800 (PST) Received: from pb-smtp20.pobox.com (unknown [127.0.0.1]) by pb-smtp20.pobox.com (Postfix) with ESMTP id BEABF19103C; Mon, 7 Mar 2022 13:15:28 -0500 (EST) (envelope-from junio@pobox.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=pobox.com; h=from:to:cc :subject:references:date:in-reply-to:message-id:mime-version :content-type; s=sasl; bh=MYWkxYDy8nlV12ZlVCU8N+hhcuzVgYd6DUXlr4 HsoOM=; b=jEb9zwhEcnYAz20p7fdJSAe1QUfYn+31FLi1bwHsJDB6tfAEWJ1SsX Ox0ndCqnCemDZXfvelnjALi5gT607U4K1P5FBJnMEpxWiN77UxWm87FOXFPV3hSg 2yVkJ7deL7mZ/ezlt4BXx8vCUtoUdtRjN60DM5gpf+yzKXzYLSMxo= Received: from pb-smtp20.sea.icgroup.com (unknown [127.0.0.1]) by pb-smtp20.pobox.com (Postfix) with ESMTP id A19DD19103B; Mon, 7 Mar 2022 13:15:28 -0500 (EST) (envelope-from junio@pobox.com) Received: from pobox.com (unknown [35.230.65.123]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pb-smtp20.pobox.com (Postfix) with ESMTPSA id EC99019103A; Mon, 7 Mar 2022 13:15:24 -0500 (EST) (envelope-from junio@pobox.com) From: Junio C Hamano To: Tao Klerks Cc: git , =?utf-8?B?w4Z2YXIgQXJuZmrDtnLDsA==?= Bjarmason , Jeff Hostetler Subject: Re: [PATCH v3 0/2] Reduce explicit sleep calls in t7063 untracked cache tests References: Date: Mon, 07 Mar 2022 10:15:24 -0800 In-Reply-To: (Tao Klerks's message of "Mon, 7 Mar 2022 06:37:02 +0100") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.2 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-Pobox-Relay-ID: 8F3D8C00-9E42-11EC-A738-C85A9F429DF0-77302942!pb-smtp20.pobox.com Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org Tao Klerks writes: > On Sun, Mar 6, 2022 at 10:57 PM Junio C Hamano wrote: >> >> Tao Klerks writes: >> >> > I see that in the latest "what's coming" update, this patch series is >> > listed as expecting reroll, but as far as I can see there have been no >> > comments since I sent this V3 out. >> >> I see reference on the source: line for that topic in the >> "What's cooking" report you are referring to, so I suspect I have >> been too busy and haven't got around to replacing it with , >> perhaps? >> > Eek, my apologies. I will remember to check that! No need to apologize. It often happens that I forget to update the status of a series after a new iteration replaces the old one when sending out a new issue of the "What's cooking" report. It is very much appreciated to be watchful and report such mistakes when you notice it. This time, it turns out that what happened was that I updated the "What's cooking" report and sent it out, and then continued working for the rest of the day to queue new topics and replace existing ones. And when you pinged me, I already had queued. To me, judging from the exchanges between you and Jeff Hostetler, the topic at v3 seems to be ready for 'next', so let me mark it as such in the draft of the next issue of "What's cooking" I keep locally. Thanks.