Received: by 2002:ac0:a5a7:0:0:0:0:0 with SMTP id m36-v6csp1285672imm; Fri, 27 Jul 2018 14:35:28 -0700 (PDT) X-Google-Smtp-Source: AAOMgpcg94U0Oq4SEnMjZU3p1G6QSDd+KdbKbDICnqA32JGeQeZe6fVws1jFgkdgfKypSHaTt1aU X-Received: by 2002:a62:9849:: with SMTP id q70-v6mr8191435pfd.178.1532727328384; Fri, 27 Jul 2018 14:35:28 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1532727328; cv=none; d=google.com; s=arc-20160816; b=d81z+sWvI0XRak3BpA0FRBRbZlw34OdGd1eBrjGgBDiY+cermREL9Vnxkb8Jfv1NIF 6uujki44RJ1gHlNW0Lw1v0koi2f2wQ/67BTU9OfSo/GpSp1GpVWQvTNuimJLh2rP7e7m dBWZHnSBTVj7Sjc6ZLaS26Ua8fSzL397NOEAK9HASzqIYqPAwMCH/E23OEGmbuYxAe63 YgFU/fRS6yPjnY1B9T6Azi7IJWF6PiMf6zr1yIFAs0MkoQXyHYnK+LKrHBFhtLmi3nHG a/ZwL/t2b5Jq4nT1fd7HJBPMGN2ohRjvjU/W9z3YqaRYXRVu/Viv6vmiS7De6qzeUs6g ulyw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :organization:references:in-reply-to:message-id:subject:cc:to:from :date:arc-authentication-results; bh=1DT53eDjSTakdSt71H1vZDbAdJxhU17bgjaJtNz0KJU=; b=i1aMGacHxOLnrNceij9ITfFrIn+eTkTV43Nk5tyYw+Po47SKQsVREdsK1CiRUlohmw BN06KR/S1yCcQ445qgYr9cKvyPgaroHmELvTJlAAPraceXeUliTVzO94bLjaZzIipJVq 9/ODlm5sy5caIZx8vXB4nI9fxnfT9QrSKSzFWiO0h0yZhunqadaYLyPX1QHZMkAW1jW3 APl/LBq3+kMS16eonJXenROYzYMJNSGQ+y/lUI738wPyNH7zTUmHVVRa3UY2xqik+D6p N06luek4garysl+QRcojm9rO8HlhzOiNkn96RU9TKXTHx1JLtPIiCa++7gP+1Nar1dIf 01wA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id r2-v6si4621097pgd.138.2018.07.27.14.35.13; Fri, 27 Jul 2018 14:35:28 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2389731AbeG0W6L (ORCPT + 99 others); Fri, 27 Jul 2018 18:58:11 -0400 Received: from ms.lwn.net ([45.79.88.28]:40674 "EHLO ms.lwn.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2389523AbeG0W6L (ORCPT ); Fri, 27 Jul 2018 18:58:11 -0400 Received: from lwn.net (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 ED82330D; Fri, 27 Jul 2018 21:34:25 +0000 (UTC) Date: Fri, 27 Jul 2018 15:34:24 -0600 From: Jonathan Corbet To: Federico Vaga Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, Alessia Mantegazza Subject: Re: [PATCH 2/2] doc:it_IT: translation for kernel-hacking Message-ID: <20180727153424.7bba09ce@lwn.net> In-Reply-To: <1944849.qmSSJrysef@pcbe13614> References: <20180706220517.28623-1-federico.vaga@vaga.pv.it> <20180706220517.28623-3-federico.vaga@vaga.pv.it> <20180726162330.786826cf@lwn.net> <1944849.qmSSJrysef@pcbe13614> Organization: LWN.net MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 27 Jul 2018 09:46:47 +0200 Federico Vaga wrote: > Generally speaking, how readers can understand > how old is a document or if it still correct (in the sense that the document > and the correspondent code are in sync)? We don't have a good answer to that, really. Some of our docs are up-to-the-second current, and others still talk about how to find out which vacuum tube has gone bad in your system. It's a trap for our readers, unfortunately. My plan has been to try to bring some more order to Documentation/ first, hopefully cleaning things up a bit on the way. > How this is handled? Just by enforcing people to update > the documentation when they change, for example, an interface that has been > documented? magari ... talk of such enforcement is a recurring thing, but nobody has the will to actually do that. jon