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=0.3 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 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 686EA1F670 for ; Wed, 16 Feb 2022 01:01:41 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230361AbiBPBAt (ORCPT ); Tue, 15 Feb 2022 20:00:49 -0500 Received: from mxb-00190b01.gslb.pphosted.com ([23.128.96.19]:55018 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S245223AbiBPBAm (ORCPT ); Tue, 15 Feb 2022 20:00:42 -0500 Received: from pb-smtp2.pobox.com (pb-smtp2.pobox.com [64.147.108.71]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 4799CE98D0 for ; Tue, 15 Feb 2022 17:00:31 -0800 (PST) Received: from pb-smtp2.pobox.com (unknown [127.0.0.1]) by pb-smtp2.pobox.com (Postfix) with ESMTP id 95725129771; Tue, 15 Feb 2022 20:00:30 -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=xPDbndLfjFAdeSYx+aO4UUYbNdUXHU5UmVMek1 FpG8I=; b=EDFQ6m4yFytez1nwThkIsJYVq+CpOy4C33dgUKXoNpmy41rYG4Rehr TGNYcDpNMgdy9ZMHya0AYGEztOxdeKysg8mx3LgFJ38ZuhTSEnxUcST6Hxpqb43v nF1HfZx5ZgM0trU60EVYbH6oS1YI7GUjblNJhXE7PJa9EESLJp1NU= Received: from pb-smtp2.nyi.icgroup.com (unknown [127.0.0.1]) by pb-smtp2.pobox.com (Postfix) with ESMTP id 8DA13129770; Tue, 15 Feb 2022 20:00:30 -0500 (EST) (envelope-from junio@pobox.com) Received: from pobox.com (unknown [35.185.212.55]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pb-smtp2.pobox.com (Postfix) with ESMTPSA id EC32212976F; Tue, 15 Feb 2022 20:00:29 -0500 (EST) (envelope-from junio@pobox.com) From: Junio C Hamano To: "Jeff Hostetler via GitGitGadget" Cc: git@vger.kernel.org, Jeff Hostetler Subject: Re: [PATCH 00/23] Builtin FSMonitor Part 3 References: Date: Tue, 15 Feb 2022 17:00:28 -0800 In-Reply-To: (Jeff Hostetler via GitGitGadget's message of "Tue, 15 Feb 2022 15:59:10 +0000") 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: D5E37B44-8EC3-11EC-9237-CB998F0A682E-77302942!pb-smtp2.pobox.com Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org "Jeff Hostetler via GitGitGadget" writes: > Here is part 3 of my builtin FSMonitor series. > > Part 3 builds upon part 2 (jh/builtin-fsmonitor-part2) which is currently in > "seen", so this series should be considered a preview until part 2 moves to > "next". (And part 2 should not graduate to "master" without this part.) > > Part 2 established the client code (used by commands like git status) and an > MVP implementation of the FSMonitor daemon. This was sufficient to test the > concepts and basic functionality. Sounds like part 2 is sufficiently done to be eligible for being in 'master', waiting for an improved daemon, no? Have people been reviewing the patches in part 2? I haven't had a chance to take a deeper look myself. Thanks.