From mboxrd@z Thu Jan 1 00:00:00 1970 From: Scott Wood Subject: Re: Device tree binding documentation Date: Tue, 28 Oct 2008 12:02:11 -0500 Message-ID: <49074593.1040008@freescale.com> References: <9696D7A991D0824DBA8DFAC74A9C5FA3047E572F@az33exm25.fsl.freescale.net> <490744B1.2000602@genesi-usa.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <490744B1.2000602-sEEEE4iEDtaXzmuOJsdVMQ@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: devicetree-discuss-bounces+gldd-devicetree-discuss=m.gmane.org-mnsaURCQ41sdnm+yROfE0A@public.gmane.org Errors-To: devicetree-discuss-bounces+gldd-devicetree-discuss=m.gmane.org-mnsaURCQ41sdnm+yROfE0A@public.gmane.org To: Matt Sealey Cc: Hugh Blemings , Benjamin Herrenschmidt , Anton Vorontsov , devicetree-discuss list List-Id: devicetree@vger.kernel.org Matt Sealey wrote: > Maintaining them as text for the development process is good but > they need to be *published* as the ePAPR binding is *published*, > so that you can say.. "hey, this is a canonical reference on a > dead tree, my platform confirms to the ePAPR MPC5200B device > tree binding V1.0 that I ordered from the Freescale website", > instead of "my platform conforms to git commit fab927fe363ac2a872bb872" The latter is actually much less subject to change... :-) -Scott