From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755300AbcDMSq0 (ORCPT ); Wed, 13 Apr 2016 14:46:26 -0400 Received: from tex.lwn.net ([70.33.254.29]:53238 "EHLO vena.lwn.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754264AbcDMSqZ (ORCPT ); Wed, 13 Apr 2016 14:46:25 -0400 Date: Wed, 13 Apr 2016 12:46:22 -0600 From: Jonathan Corbet To: "Paul E. McKenney" Cc: SeongJae Park , Ingo Molnar , Linus Torvalds , Andrew Morton , Greg Kroah-Hartman , "linux-kernel@vger.kernel.org" , jiangshanlai@gmail.com, dipankar@in.ibm.com, mathieu.desnoyers@efficios.com, josh@joshtriplett.org, tglx@linutronix.de, peterz@infradead.org, rostedt@goodmis.org, David Howells , edumazet@google.com, dvhart@linux.intel.com, fweisbec@gmail.com, oleg@redhat.com, bobby.prani@gmail.com, Peter Zijlstra , "H. Peter Anvin" Subject: Re: [PATCH memory-barriers.txt 6/7] documentation: Add Korean translation Message-ID: <20160413124622.584ff77e@lwn.net> In-Reply-To: <20160413124953.GA3568@linux.vnet.ibm.com> References: <20160412155228.GA27257@linux.vnet.ibm.com> <1460476375-27803-6-git-send-email-paulmck@linux.vnet.ibm.com> <20160413063805.GA14197@gmail.com> <20160413124953.GA3568@linux.vnet.ibm.com> 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 List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 13 Apr 2016 05:49:53 -0700 "Paul E. McKenney" wrote: > We currently do > not have a good way to tell which translations are no longer keeping up > and thus need to be pruned, and we would need one. So I have to play the devil's advocate a bit here... we don't currently have a mechanism to tell us which files in Documentation/ in general are not keeping up and needing to be pruned[0]. But we don't use that as a reason to block documentation submissions in general. It's a bit harder for a random passer-by to determine that a translation is out of sync[1], but we do have a version control system that can help us to see that, at least, somebody is occasionally updating things. It's not a complete black box. I would argue in favor of including translations when somebody has taken the time to create them. They cost little and can be helpful for developers who are struggling with both the kernel code and the English language. jon [0] OK, a real devil's advocate would say that "ls" or even "echo Documentation/*" is sufficient. [1] Though, perhaps, many or most developers can make just as much sense of a version of memory-barriers.txt in a language they don't understand as they can with the original. :)