From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from atuin.qyliss.net (localhost [IPv6:::1]) by atuin.qyliss.net (Postfix) with ESMTP id 9B6F2870B; Tue, 04 Aug 2026 21:32:27 +0000 (UTC) Received: by atuin.qyliss.net (Postfix, from userid 993) id E466B8703; Tue, 04 Aug 2026 21:32:25 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 4.0.1 (2024-03-26) on atuin.qyliss.net X-Spam-Level: ** X-Spam-Status: No, score=2.4 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,DMARC_MISSING,FROM_SUSPICIOUS_NTLD,PDS_OTHER_BAD_TLD, SPF_HELO_NONE autolearn=no autolearn_force=no version=4.0.1 Received: from mail-108-mta244.mxroute.com (mail-108-mta244.mxroute.com [136.175.108.244]) by atuin.qyliss.net (Postfix) with ESMTPS id 8B0EB86BC for ; Tue, 04 Aug 2026 21:32:24 +0000 (UTC) Received: from filter006.mxroute.com ([136.175.111.3] filter006.mxroute.com) (Authenticated sender: mN4UYu2MZsgR) by mail-108-mta244.mxroute.com (ZoneMTA) with ESMTPSA id 19fceb11ac4000c8ef.002 for (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384); Tue, 04 Aug 2026 21:32:21 +0000 X-Zone-Loop: bfa4dbbb9215123dc03b4040d7d9d5c966df204bcb80 X-Originating-IP: [136.175.111.3] DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gagarin.work; s=x; h=Content-Transfer-Encoding:Content-Type:In-Reply-To: From:References:To:Subject:MIME-Version:Date:Message-ID:Sender:Reply-To:Cc: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=hMaEY8bcJ5jt8jgfIZP+9ziaCcLXGXyj0aD/ghpp/Kw=; b=sUvAGCP4cK35k99TmYXFET1U2j CIshgxi2aVvWNuIxopL/ShOEECPM2qxafzzU73peJVcoP3Rzi1CR4+WS3qo1xqrKCLXMYWeSIXQV9 eNmFIiBQdJr41MB34+m+lnd2Y2ZwvRsSHU2SmMuoGf4og4bDh4jdEeDyAw1pIvBZemAq+PdY5B//5 0m1x6jxdr1+sDh9StPCjhSLP5ZzlMo0GkGns8dq/hPQvCa3wauWvNQ61rdmDL3BCnoWV3iLO8b1Ly 4a+0PxjSNR6BgYI/8Ae20cTke8An+MuTAk7mSGdgf5+AWjmVfC7w2PO0Z1FCG7dgxgH/1GxiI0xzF jjwn5m/Q==; Message-ID: Date: Tue, 4 Aug 2026 23:32:14 +0200 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH] Documentation: adopt a consistent nav_order format To: devel@spectrum-os.org, Alyssa Ross References: <20260804162458.174944-1-hi@alyssa.is> Content-Language: en-US From: Valentin Gagarin In-Reply-To: <20260804162458.174944-1-hi@alyssa.is> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Authenticated-Id: valentin@gagarin.work Message-ID-Hash: ROU6MH2DVJHGCJ4NY63ZFJHOM6DNWU26 X-Message-ID-Hash: ROU6MH2DVJHGCJ4NY63ZFJHOM6DNWU26 X-MailFrom: valentin@gagarin.work X-Mailman-Rule-Hits: member-moderation X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; header-match-devel.spectrum-os.org-0; header-match-devel.spectrum-os.org-1; header-match-devel.spectrum-os.org-2; header-match-devel.spectrum-os.org-3; header-match-devel.spectrum-os.org-4; emergency X-Mailman-Version: 3.3.10 Precedence: list List-Id: Patches and low-level development discussion Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: We may want to use an explicit table of contents instead in the future, since fumbling with the order via those numbers is needlessly cumbersome. But that would require thinking a few things through, and this looks good for now. Reviewed-by: Valentin Gagarin