From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 4C354C61DA4 for ; Wed, 15 Mar 2023 22:18:59 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231167AbjCOWS6 (ORCPT ); Wed, 15 Mar 2023 18:18:58 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:60238 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231560AbjCOWSy (ORCPT ); Wed, 15 Mar 2023 18:18:54 -0400 Received: from mga17.intel.com (mga17.intel.com [192.55.52.151]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 86D7E2BEC4; Wed, 15 Mar 2023 15:18:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1678918713; x=1710454713; h=message-id:date:mime-version:subject:to:cc:references: from:in-reply-to:content-transfer-encoding; bh=fU4QSBmq06kLp0HuxVosNJEKUx3vKXjpqUJcfSNehIg=; b=R8eYLpwl6zOBXVjVGOh4kuc1mwc666w4yFo70wICN3yAsyT7Z8O3xNmp ek5Yv5NAtbSOyscaqkrIY4ntZWeH1TZJGhOJZZMs0YaCzope36rXVDeJu MOh1hznOPa5G7Ghm7wqP5UsoNhn9FKv1IRa9vWOQZEVx+1bpeyk+bilbQ +/Gx6653uQJLwIkBcHUQF78YTj9oDFjQQqTPPPjJaJ9QAQBuiFemlvqTm vgPQVCWgPC1YcdkIFkm9ld6z7Lv1H8FCp+fTc9XOPtExCFDnzgRIbm4Or j8rB0GJ6ZVOJtY0BmvtSiAWzwBojwTlt/oKnfddN+nJdYz3FWIYJc3wHj A==; X-IronPort-AV: E=McAfee;i="6500,9779,10650"; a="318226006" X-IronPort-AV: E=Sophos;i="5.98,262,1673942400"; d="scan'208";a="318226006" Received: from orsmga008.jf.intel.com ([10.7.209.65]) by fmsmga107.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 15 Mar 2023 15:18:28 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6500,9779,10650"; a="709832226" X-IronPort-AV: E=Sophos;i="5.98,262,1673942400"; d="scan'208";a="709832226" Received: from arnabch1-mobl.amr.corp.intel.com (HELO [10.209.44.101]) ([10.209.44.101]) by orsmga008-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 15 Mar 2023 15:18:28 -0700 Message-ID: Date: Wed, 15 Mar 2023 15:18:28 -0700 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.7.1 Subject: Re: [PATCH RFC 0/2] Begin reorganizing the arch documentation Content-Language: en-US To: Jonathan Corbet , linux-doc@vger.kernel.org Cc: linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org, Thomas Gleixner , Ingo Molnar , Dave Hansen , x86@kernel.org, Peter Zijlstra , Borislav Petkov References: <20230315211523.108836-1-corbet@lwn.net> From: Dave Hansen In-Reply-To: <20230315211523.108836-1-corbet@lwn.net> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-arch@vger.kernel.org On 3/15/23 14:15, Jonathan Corbet wrote: > On the other hand, it *is* a fair amount of churn. If it's more than > people can handle, I'll quietly back away and we'll muddle along as we have > been; this isn't something I'm going to dig in my heels over. I'm not fundamentally opposed to this. It'll probably cost me a few keystrokes in moments of confusion, but that's the price of progress. :) Things in Documentation/ have also been mobile enough in recent years that I tend to "find Documentation | grep something" rather than try to remember the paths for things. Adding an arch/ in there won't hurt anything. > Also, it is worth noting that, while the rendered HTML looks the same, > links that went to Documentation/x86 (on https://kernel.org, say) will be > broken by this change. We have never considered whether we care about > preserving external links to the rendered docs on kernel.org or not; I > don't think we should break them without thinking about it. I don't think this is a big deal. Folks that are doing explicit versions: https://www.kernel.org/doc/html/v6.0/x86/ won't break and folks that are using "latest": https://www.kernel.org/doc/html/latest/x86/ are kinda already playing with fire. I guess we could ask the kernel.org admins to see how many 404's folks get after the docs get moved. They could _theoretically_ redirect users from the old to new URL: doc/html/latest/x86 => doc/html/latest/arch/x86 but I doubt it's worth it for this one little directory.