From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on archive.lwn.net X-Spam-Level: X-Spam-Status: No, score=-6.0 required=5.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,RCVD_IN_DNSWL_HI autolearn=ham autolearn_force=no version=3.4.1 Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by archive.lwn.net (Postfix) with ESMTP id 395E97D584 for ; Fri, 24 Aug 2018 13:21:58 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727415AbeHXQ4d (ORCPT ); Fri, 24 Aug 2018 12:56:33 -0400 Received: from ms.lwn.net ([45.79.88.28]:32798 "EHLO ms.lwn.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726883AbeHXQ4c (ORCPT ); Fri, 24 Aug 2018 12:56:32 -0400 Received: from localhost.localdomain (localhost [127.0.0.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ms.lwn.net (Postfix) with ESMTPSA id CFBCE2C1; Fri, 24 Aug 2018 13:21:52 +0000 (UTC) Date: Fri, 24 Aug 2018 07:21:50 -0600 From: Jonathan Corbet To: Federico Vaga Cc: , Subject: Re: Italian translations and broken links Message-ID: <20180824072150.51b890c8@lwn.net> In-Reply-To: <3898461.lmkq0IsokZ@pcbe13614> References: <3898461.lmkq0IsokZ@pcbe13614> Organization: LWN.net X-Mailer: Claws Mail 3.16.0 (GTK+ 2.24.32; x86_64-redhat-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8bit Sender: linux-doc-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-doc@vger.kernel.org On Fri, 24 Aug 2018 13:51:18 +0200 Federico Vaga wrote: > Since there are many documents, this take time and perhaps we can already push > the ones which are ready. > > My big dilemma is (which is more general): what about broken references? Do we > keep broken links which we know they will be correct in the future? Or, do we > remove all broken links and we add them back only when they work (if we > remember)? We want the kernel to be as close to release-ready as it can be at any time, that includes the docs. So please no broken links. It's a bit more work to keep things coherent, but it's what we need to do in the long run. Thanks, jon