From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeff King Subject: Re: [PATCH] doc: fix unmatched code fences Date: Wed, 13 May 2015 00:36:09 -0400 Message-ID: <20150513043609.GA6038@peff.net> References: <1431451400-1447-1-git-send-email-jn.avila@free.fr> <20150513021556.GA4160@peff.net> <20150513034553.GA25025@peff.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Cc: Jean-Noel Avila , git@vger.kernel.org To: Junio C Hamano X-From: git-owner@vger.kernel.org Wed May 13 06:36:18 2015 Return-path: Envelope-to: gcvg-git-2@plane.gmane.org Received: from vger.kernel.org ([209.132.180.67]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1YsOP3-0000td-Ge for gcvg-git-2@plane.gmane.org; Wed, 13 May 2015 06:36:17 +0200 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750842AbbEMEgN (ORCPT ); Wed, 13 May 2015 00:36:13 -0400 Received: from cloud.peff.net ([50.56.180.127]:57581 "HELO cloud.peff.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1750709AbbEMEgM (ORCPT ); Wed, 13 May 2015 00:36:12 -0400 Received: (qmail 721 invoked by uid 102); 13 May 2015 04:36:11 -0000 Received: from Unknown (HELO peff.net) (10.0.1.1) by cloud.peff.net (qpsmtpd/0.84) with SMTP; Tue, 12 May 2015 23:36:11 -0500 Received: (qmail 6743 invoked by uid 107); 13 May 2015 04:36:10 -0000 Received: from sigill.intra.peff.net (HELO sigill.intra.peff.net) (10.0.0.7) by peff.net (qpsmtpd/0.84) with SMTP; Wed, 13 May 2015 00:36:10 -0400 Received: by sigill.intra.peff.net (sSMTP sendmail emulation); Wed, 13 May 2015 00:36:09 -0400 Content-Disposition: inline In-Reply-To: Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org Archived-At: On Tue, May 12, 2015 at 09:32:45PM -0700, Junio C Hamano wrote: > Jeff King writes: > > >> It obviously is not a title underline as the lengths are vastly > >> different. > > > > Yes, but Python Asciidoc allows the lengths to differ. > > Hmmm, I thought the title underline was a bit more strict. I do > recall having to fix manual pages for many commands, but we do not > add new commands these days anymore, so perhaps things have changed > since then. I think it is loose in AsciiDoc and strict in AsciiDoctor, so we have been slowly making sure they are all consistent. And we missed one, which will be in the series I'll send in a moment. :) I suspect the potential ambiguity is one of the reasons that AsciiDoctor went with the stricter rule. -Peff