From mboxrd@z Thu Jan 1 00:00:00 1970 From: Junio C Hamano Subject: Re: [PATCH] Fix indentation problem in git-ls-files(1) Date: Sun, 07 Mar 2010 10:38:27 -0800 Message-ID: <7veijwrn8c.fsf@alter.siamese.dyndns.org> References: <7v3a0fr740.fsf@alter.siamese.dyndns.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: Andreas Schwab , git@vger.kernel.org To: Mark Lodato X-From: git-owner@vger.kernel.org Sun Mar 07 19:38:59 2010 Return-path: Envelope-to: gcvg-git-2@lo.gmane.org Received: from vger.kernel.org ([209.132.180.67]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1NoLNR-0000NS-OF for gcvg-git-2@lo.gmane.org; Sun, 07 Mar 2010 19:38:58 +0100 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754694Ab0CGSii convert rfc822-to-quoted-printable (ORCPT ); Sun, 7 Mar 2010 13:38:38 -0500 Received: from a-pb-sasl-quonix.pobox.com ([208.72.237.25]:56607 "EHLO sasl.smtp.pobox.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754683Ab0CGSig convert rfc822-to-8bit (ORCPT ); Sun, 7 Mar 2010 13:38:36 -0500 Received: from sasl.smtp.pobox.com (unknown [127.0.0.1]) by a-pb-sasl-quonix.pobox.com (Postfix) with ESMTP id C257BA0E9F; Sun, 7 Mar 2010 13:38:35 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=pobox.com; h=to:cc:subject :references:from:date:message-id:mime-version:content-type :content-transfer-encoding; s=sasl; bh=2pMBxptUpA7ozgv6v9pmXKeg3 X4=; b=hyCCVkQ9c2nS1wW5e8YIIKJBZe6vjA/QEV3Qlk4CGiYmOF6K296ZGo18P 1XnYTfaWVbI71mtOr66ZZD/vF5TQvn5NQMMXoWKStMVzSi8vScU9UMzcx6O9KcXp vkByEaBkD+3mtkfyfRohZcBfpp/BloYuM7lcEF9EaOdTXasB94= DomainKey-Signature: a=rsa-sha1; c=nofws; d=pobox.com; h=to:cc:subject :references:from:date:message-id:mime-version:content-type :content-transfer-encoding; q=dns; s=sasl; b=meev0mBNYmTR+oClAEf +seZOTmtE3ofpRpnfVX8o3kgsIXj4GBVRdnLcEoSkcWeSFoapqaNhitSaOtZe6Az 3M/q/jJ68C88ej4RyBMfFKD9j4T+KHFqpHZXI+EQYbGpOLdMEI2Qi/4y5IBoJP+e zJtEALYVq/jUcyRV7b95wIZ0= Received: from a-pb-sasl-quonix. (unknown [127.0.0.1]) by a-pb-sasl-quonix.pobox.com (Postfix) with ESMTP id 8F95BA0E9E; Sun, 7 Mar 2010 13:38:32 -0500 (EST) Received: from pobox.com (unknown [68.225.240.211]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by a-pb-sasl-quonix.pobox.com (Postfix) with ESMTPSA id D0BC8A0E9C; Sun, 7 Mar 2010 13:38:28 -0500 (EST) User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.2 (gnu/linux) X-Pobox-Relay-ID: A1BE3740-2A18-11DF-A419-D033EE7EF46B-77302942!a-pb-sasl-quonix.pobox.com Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org Archived-At: Mark Lodato writes: > On Fri, Mar 5, 2010 at 5:08 AM, Andreas Schwab wrote: >> Junio C Hamano writes: >> >>> Both [horizontal] and three colons are something we never have used= in the >>> existing documentation set. =C2=A0How confident are you that variou= s versions >>> of deployed AsciiDoc people would use all support this? >> >> I'm sorry, but I have no idea. =C2=A0I just looked at the user guide= on the >> asciidoc home page, which contais no version information. > > Yes, the documentation is lacking here. I believe we official suppor= t > AsciiDoc 8.2.7 - this is what the builds on kernel.org use. =46YI, the machine documentation set is autogenerated at k.org uses 8.2= =2E5 right now, not 8.2.7.. > Here's a cheatsheet for that version: > > http://powerman.name/doc/asciidoc-827 Thanks for a link. > Hopefully the following will clarify things for the future: > ... > Perhaps it would be a good idea to add an Asciidoc section to > Documentation/CodingGuidelines? This could clear up these sorts of > questions, and also cover conventions used in the manual: what name t= o > give metavariables, when to use backticks, when to use single quotes, > etc. The only rule we had so far is "try to mimic existing text around what = you are changing", and "don't try to be original nor fancy by using feature= s that are not used in existing text anywhere", I agree it would be helpf= ul to have more concrete tips on what to avoid, and conventions on what particular typesetting conventions we chose for various parts of speech= =2E