git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Mark Lodato <lodatom@gmail.com>
Cc: Andreas Schwab <schwab@linux-m68k.org>, git@vger.kernel.org
Subject: Re: [PATCH] Fix indentation problem in git-ls-files(1)
Date: Sun, 07 Mar 2010 10:38:27 -0800	[thread overview]
Message-ID: <7veijwrn8c.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: ca433831003070927h4c3e24e1m75c7be88355f9663@mail.gmail.com

Mark Lodato <lodatom@gmail.com> writes:

> On Fri, Mar 5, 2010 at 5:08 AM, Andreas Schwab <schwab@linux-m68k.org> wrote:
>> Junio C Hamano <gitster@pobox.com> writes:
>>
>>> Both [horizontal] and three colons are something we never have used in the
>>> existing documentation set.  How confident are you that various versions
>>> of deployed AsciiDoc people would use all support this?
>>
>> I'm sorry, but I have no idea.  I 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 support
> AsciiDoc 8.2.7 - this is what the builds on kernel.org use.

FYI, the machine documentation set is autogenerated at k.org uses 8.2.5
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 to
> 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 features
that are not used in existing text anywhere", I agree it would be helpful
to have more concrete tips on what to avoid, and conventions on what
particular typesetting conventions we chose for various parts of speech.

  reply	other threads:[~2010-03-07 18:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-04 14:32 [PATCH] Fix indentation problem in git-ls-files(1) Andreas Schwab
2010-03-04 23:37 ` Junio C Hamano
2010-03-05 10:08   ` Andreas Schwab
2010-03-07 17:27     ` Mark Lodato
2010-03-07 18:38       ` Junio C Hamano [this message]
2010-03-15 22:49       ` Andreas Schwab
2010-03-15 23:12         ` Junio C Hamano
2010-03-16  7:05         ` Johannes Sixt
2010-03-16 19:47           ` Andreas Schwab
2010-03-17  6:47             ` Johannes Sixt
2010-03-19 18:55               ` Andreas Schwab
2010-03-20 14:01                 ` Junio C Hamano

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7veijwrn8c.fsf@alter.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=lodatom@gmail.com \
    --cc=schwab@linux-m68k.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).