git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Rast <trast@student.ethz.ch>
To: Ramkumar Ramachandra <artagnon@gmail.com>
Cc: <git@vger.kernel.org>
Subject: Re: [PATCH] Fix bad quoting in documentation
Date: Sat, 16 Jan 2010 11:20:11 +0100	[thread overview]
Message-ID: <201001161120.14846.trast@student.ethz.ch> (raw)
In-Reply-To: <f3271551001160002r25cb0ac7hc96891f4af22bd03@mail.gmail.com>

Ramkumar Ramachandra wrote:
> Reported by Frédéric Brière <fbriere@fbriere.net> through
> http://bugs.debian.org/540001

Does this fix anything except the instances already handled by 71c020c
(Disable asciidoc 8.4.1+ semantics for `{plus}` and friends,
2009-07-25)?

If so, please point them out for easier review.

If not, please tell the debian guys to set ASCIIDOC8=YesPlease when
building the docs.

-- 
Thomas Rast
trast@{inf,student}.ethz.ch

  reply	other threads:[~2010-01-16 10:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-16  8:02 [PATCH] Fix bad quoting in documentation Ramkumar Ramachandra
2010-01-16 10:20 ` Thomas Rast [this message]
2010-01-16 11:00   ` Ramkumar Ramachandra
2010-01-16 11:58     ` Teemu Likonen

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=201001161120.14846.trast@student.ethz.ch \
    --to=trast@student.ethz.ch \
    --cc=artagnon@gmail.com \
    --cc=git@vger.kernel.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).