All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: Daniel Vetter <daniel.vetter@ffwll.ch>,
	Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH i-g-t 1/2] lib: avoid < in gtkdoc comments
Date: Mon, 04 Dec 2017 15:53:12 +0200	[thread overview]
Message-ID: <1512395592.4394.42.camel@linux.intel.com> (raw)
In-Reply-To: <20171129111755.25825-1-daniel.vetter@ffwll.ch>

On Wed, 2017-11-29 at 12:17 +0100, Daniel Vetter wrote:
> For reasons entirely not clear to me meson gtkdoc runs in strict
> xml parsing mode, whereas automake gtkdoc doesn't. And gtkdoc itself
> is tooooooooo dense to correctly escape this stuff.
> 
> Paper around this.
> 
> Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>

&lt;foo> looks trippy.

As we're not trying to document HTML stuff, maybe simly <foo> ->
${foo}. I'm pretty sure everyone will be comfortable with that
notation.

Regards, Joonas
-- 
Joonas Lahtinen
Open Source Technology Center
Intel Corporation
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

      parent reply	other threads:[~2017-12-04 13:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-29 11:17 [PATCH i-g-t 1/2] lib: avoid < in gtkdoc comments Daniel Vetter
2017-11-29 11:17 ` [PATCH i-g-t 2/2] meson: gtkdoc support Daniel Vetter
2017-11-29 11:39 ` ✓ Fi.CI.BAT: success for series starting with [1/2] lib: avoid < in gtkdoc comments Patchwork
2017-11-29 12:57 ` ✓ Fi.CI.IGT: " Patchwork
2017-12-04 13:53 ` Joonas Lahtinen [this message]

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=1512395592.4394.42.camel@linux.intel.com \
    --to=joonas.lahtinen@linux.intel.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=intel-gfx@lists.freedesktop.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.