From owner-svn-src-all@FreeBSD.ORG Sun Apr 19 15:44:55 2015 Return-Path: Delivered-To: svn-src-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 774C4CB7; Sun, 19 Apr 2015 15:44:55 +0000 (UTC) Received: from relay.mailchannels.net (tkt-001-i373.relay.mailchannels.net [174.136.5.175]) by mx1.freebsd.org (Postfix) with ESMTP id BA9EEA62; Sun, 19 Apr 2015 15:44:53 +0000 (UTC) X-Sender-Id: duocircle|x-authuser|hippie Received: from smtp6.ore.mailhop.org (ip-10-204-4-183.us-west-2.compute.internal [10.204.4.183]) by relay.mailchannels.net (Postfix) with ESMTPA id A984F608FE; Sun, 19 Apr 2015 15:44:50 +0000 (UTC) X-Sender-Id: duocircle|x-authuser|hippie Received: from smtp6.ore.mailhop.org (smtp6.ore.mailhop.org [10.45.8.167]) (using TLSv1 with cipher DHE-RSA-AES256-SHA) by 0.0.0.0:2500 (trex/5.4.8); Sun, 19 Apr 2015 15:44:51 +0000 X-MC-Relay: Neutral X-MailChannels-SenderId: duocircle|x-authuser|hippie X-MailChannels-Auth-Id: duocircle X-MC-Loop-Signature: 1429458290817:3322840153 X-MC-Ingress-Time: 1429458290817 Received: from c-73-34-117-227.hsd1.co.comcast.net ([73.34.117.227] helo=ilsoft.org) by smtp6.ore.mailhop.org with esmtpsa (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.82) (envelope-from ) id 1YjrOs-0001PF-0d; Sun, 19 Apr 2015 15:44:50 +0000 Received: from revolution.hippie.lan (revolution.hippie.lan [172.22.42.240]) by ilsoft.org (8.14.9/8.14.9) with ESMTP id t3JFiktq027639; Sun, 19 Apr 2015 09:44:46 -0600 (MDT) (envelope-from ian@freebsd.org) X-Mail-Handler: DuoCircle Outbound SMTP X-Originating-IP: 73.34.117.227 X-Report-Abuse-To: abuse@duocircle.com (see https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information for abuse reporting information) X-MHO-User: U2FsdGVkX1/yctJyptgXBtlI3/rUkSaB Message-ID: <1429458286.1182.89.camel@freebsd.org> Subject: Re: svn commit: r281727 - head From: Ian Lepore To: Alexey Dokuchaev Cc: Eitan Adler , "src-committers@freebsd.org" , "svn-src-all@freebsd.org" , "svn-src-head@freebsd.org" Date: Sun, 19 Apr 2015 09:44:46 -0600 In-Reply-To: <20150419153927.GA30772@FreeBSD.org> References: <201504190716.t3J7GjmW072744@svn.freebsd.org> <20150419083451.GA79519@FreeBSD.org> <20150419153927.GA30772@FreeBSD.org> Content-Type: text/plain; charset="us-ascii" X-Mailer: Evolution 3.12.10 FreeBSD GNOME Team Port Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-AuthUser: hippie X-BeenThere: svn-src-all@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "SVN commit messages for the entire src tree \(except for " user" and " projects" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Apr 2015 15:44:55 -0000 On Sun, 2015-04-19 at 15:39 +0000, Alexey Dokuchaev wrote: > On Sun, Apr 19, 2015 at 01:42:08AM -0700, Eitan Adler wrote: > > On 19 April 2015 at 01:34, Alexey Dokuchaev wrote: > > > On Sun, Apr 19, 2015 at 07:16:45AM +0000, Eitan Adler wrote: > > >> New Revision: 281727 > > >> URL: https://svnweb.freebsd.org/changeset/base/281727 > > >> > > >> Log: > > >> README: changes and fixups > > >> Two orthogonal goals: > > >> - try to make README look a little nicer on phabricator by using > > >> Remarkup syntax for commands (using `` instead of using a > > >> closing ') > > >> - try to make README look a little nicer on github. > > > > > > FreeBSD had traditionally used both double (``...'') and single (`...') > > > to express "literal" something; I am not convinced that changing it > > > just to match GitHub's markdown warrants it. This `...` form is alien > > > to FreeBSD, and can be also confused with backquoted form of shell's > > > $(...) command substitution. > > > > Without this change, the syntax ends up being parsed very weirdly by > > both phabricator and github. That said, if there is strong precedent > > not to use the markdown syntax, and it would cause confusion, I will > > revert those changes. > > I understand your reasons. I don't think we have any strong precedent > for those things, but nor do I want to neglect the issue of markdowning > our docs... Seeing /usr/ports/CONTRIBUTING.md already made me shiver. > > Since we control our own installation of Phabricator, maybe we should > teach it to recognize ``...'' and `...' instead of converting them? > (I don't know what to do about GitHub, but I don't like the idea that > their markdown syntax inadvertently affects our files.) > > ./danfe > Indeed, chasing the fad of the day seems like a Really Bad Idea. I know people are religious about github and will bristle at labeling it a fad. People had similar feelings about sourceforge a few years ago. We wisely avoiding changing anything then, and we should do so some more. Our readme and similar files are plain ascii text. If that confuses github, then the fix needs to be applied at github. -- Ian