dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@s-opensource.com>
To: Markus Heiser <markus.heiser@darmarit.de>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
	linux-doc@vger.kernel.org,
	DRI Development <dri-devel@lists.freedesktop.org>,
	Jonathan Corbet <corbet@lwn.net>,
	Jani Nikula <jani.nikula@linux.intel.com>,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	Daniel Vetter <daniel.vetter@intel.com>
Subject: Re: [PATCH 2/6] docs-rst: automatically convert Graphviz and SVG images
Date: Thu, 2 Mar 2017 20:19:43 -0300	[thread overview]
Message-ID: <20170302201943.7c04fd29@vento.lan> (raw)
In-Reply-To: <21106153-02E4-40C8-81D1-829485BAD155@darmarit.de>

Em Thu, 2 Mar 2017 23:15:49 +0100
Markus Heiser <markus.heiser@darmarit.de> escreveu:

> Hi Daniel, hi Mauro,
> 
> I have to say, that I lost control over our thread ;)
> 
> > v3: Only sphinx 1.4 (released in Mar 2016) has patches.Figure.
> > Implement Markus suggestion for backwards compatability with earlier
> > releases. Laurent reported this, running sphinx 1.3. Solution entirely
> > untested.  
> 
> I have to come back to a more systematic work, this means;
> I have to test this v3 and consider what Mauro and you 
> already posted.

Yes, you're lost :-) The last patch Daniel Sent was v5. From his last patch:


> v4: Only sphinx 1.4 (released in Mar 2016) has patches.Figure.
> Implement Markus suggestion for backwards compatability with earlier
> releases. Laurent reported this, running sphinx 1.3. Solution entirely
> untested.
> 
> v5: Use an explicit version check (suggested by Laurent).

	https://marc.info/?l=linux-doc&m=148847115500505&w=2


Thanks,
Mauro

  reply	other threads:[~2017-03-02 23:19 UTC|newest]

Thread overview: 56+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-02 15:16 [PATCH 1/6] doc: Explain light-handed markup preference a bit better Daniel Vetter
2017-03-02 15:16 ` [PATCH 2/6] docs-rst: automatically convert Graphviz and SVG images Daniel Vetter
2017-03-02 15:20   ` Laurent Pinchart
2017-03-02 15:40   ` [PATCH] " Daniel Vetter
2017-03-02 18:06     ` Mauro Carvalho Chehab
2017-03-02 19:06       ` Markus Heiser
2017-03-02 19:34         ` Mauro Carvalho Chehab
2017-03-02 19:56           ` Mauro Carvalho Chehab
2017-03-02 21:16           ` Markus Heiser
2017-03-02 21:22             ` Mauro Carvalho Chehab
2017-03-02 19:52         ` Daniel Vetter
2017-03-02 20:04           ` Mauro Carvalho Chehab
2017-03-02 20:54             ` Mauro Carvalho Chehab
2017-03-02 21:29     ` Mauro Carvalho Chehab
2017-03-02 21:36       ` Mauro Carvalho Chehab
2017-03-02 21:47         ` Mauro Carvalho Chehab
2017-03-02 21:54           ` Markus Heiser
2017-03-03  8:54         ` Daniel Vetter
2017-03-02 22:15   ` [PATCH 2/6] " Markus Heiser
2017-03-02 23:19     ` Mauro Carvalho Chehab [this message]
2017-03-02 15:16 ` [PATCH 3/6] drm/doc: Add KMS overview graphs Daniel Vetter
2017-03-02 15:16 ` [PATCH 4/6] drm/doc: Consistent kerneldoc include order Daniel Vetter
2017-03-02 15:16 ` [PATCH 5/6] drm/doc: diagram for mode objects and properties Daniel Vetter
2017-03-02 15:16 ` [PATCH 6/6] drm/doc: atomic overview, with graph Daniel Vetter
2017-03-02 15:24   ` Gabriel Krisman Bertazi
2017-03-14 14:14     ` Daniel Vetter
2017-03-07 16:40 ` [PATCH 1/6] doc: Explain light-handed markup preference a bit better Daniel Vetter
2017-03-07 16:55   ` Jonathan Corbet
  -- strict thread matches above, loose matches on Subject: below --
2017-02-28 17:13 [PATCH 0/6] more kernel-doc patches Daniel Vetter
2017-02-28 17:13 ` [PATCH 2/6] docs-rst: automatically convert Graphviz and SVG images Daniel Vetter
2017-03-01 15:56   ` Gabriel Krisman Bertazi
2017-03-02  7:12     ` Daniel Vetter
2017-03-02  8:23       ` Markus Heiser
2017-03-02 12:26   ` Laurent Pinchart
2017-03-02 13:54     ` Daniel Vetter
2017-03-02 14:14       ` Laurent Pinchart
2017-03-02 14:58         ` Markus Heiser
2017-03-02 15:11           ` Daniel Vetter
2017-03-02 15:17             ` Laurent Pinchart
2017-03-02 15:21             ` Markus Heiser
2017-03-02 15:45               ` Mauro Carvalho Chehab
2017-03-02 15:49                 ` Mauro Carvalho Chehab
2017-03-02 16:13                   ` Markus Heiser
2017-03-02 16:29                     ` Mauro Carvalho Chehab
2017-03-02 18:16                       ` Markus Heiser
2017-03-02 18:20                         ` Jonathan Corbet
2017-03-02 18:47                           ` Markus Heiser
2017-03-02 19:09                         ` Mauro Carvalho Chehab
2017-03-02 20:16                           ` Markus Heiser
2017-03-02 20:28                             ` Mauro Carvalho Chehab
2017-03-02 15:22             ` Jonathan Corbet
2017-03-02 15:53               ` Daniel Vetter
2017-03-02 16:01                 ` Mauro Carvalho Chehab
2017-03-02 19:49                   ` Daniel Vetter
2017-03-06 10:12   ` Daniel Vetter
2017-03-06 13:13     ` Markus Heiser
2017-03-06 15:03       ` Daniel Vetter

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=20170302201943.7c04fd29@vento.lan \
    --to=mchehab@s-opensource.com \
    --cc=corbet@lwn.net \
    --cc=daniel.vetter@ffwll.ch \
    --cc=daniel.vetter@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=jani.nikula@linux.intel.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=markus.heiser@darmarit.de \
    /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).