From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:56084) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bPl8M-0007ha-0P for qemu-devel@nongnu.org; Wed, 20 Jul 2016 02:37:30 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bPl8H-0005Gq-QN for qemu-devel@nongnu.org; Wed, 20 Jul 2016 02:37:28 -0400 Received: from mx1.redhat.com ([209.132.183.28]:50263) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bPl8H-0005Gd-KV for qemu-devel@nongnu.org; Wed, 20 Jul 2016 02:37:25 -0400 From: Markus Armbruster References: <1468950439-16259-1-git-send-email-sw@weilnetz.de> Date: Wed, 20 Jul 2016 08:37:21 +0200 In-Reply-To: (Peter Maydell's message of "Tue, 19 Jul 2016 22:33:58 +0100") Message-ID: <87fur4izmm.fsf@dusky.pond.sub.org> MIME-Version: 1.0 Content-Type: text/plain Subject: Re: [Qemu-devel] [PATCH] Fix regressions caused by renaming README List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Maydell Cc: Pranith Kumar , Stefan Weil , QEMU Developer , Paolo Bonzini Peter Maydell writes: > On 19 July 2016 at 22:17, Pranith Kumar wrote: >> On Tue, Jul 19, 2016 at 4:53 PM, Peter Maydell wrote: >>> Does raise the question of whether we should be renaming >>> the file in the first place. README is the traditional >>> name and fits with all our other basically-plain-text >>> document names like COPYING, MAINTAINERS, HACKING. >>> >> >> I was hoping that this change would be helpful since mark >> down(at-least the way we have it) still looks like plain text if you >> open in a text editor. The advantage is that github repositories look >> way better since mark down is formatted well there. I am open to >> getting it reverted if it really is bothering. > > On the other hand we don't use github as our primary git > repo, and we don't try to render the markdown anywhere > in our build process. The documentation really is a > plain text file in my view, and I'm not hugely enthusiastic > about switching the filename to placate a website we > don't even use except as a backup/mirror. I'd less unenthusiastic if MarkDown worked the same everywhere. Its common core does, but how would we ensure we stick to the common core? How would we even know what the core common to the various MarkDown dialects is? Or are we ready to commit to GitHub's dialect?