All of lore.kernel.org
 help / color / mirror / Atom feed
From: Danilo Cesar Lemes de Paula <danilo.cesar@collabora.co.uk>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Michal Marek <mmarek@suse.cz>,
	Herbert Xu <herbert@gondor.apana.org.au>,
	linux-doc@vger.kernel.org, Stephan Mueller <smueller@chronox.de>,
	Daniel Vetter <daniel.vetter@ffwll.ch>,
	intel-gfx <intel-gfx@lists.freedesktop.org>,
	Randy Dunlap <rdunlap@infradead.org>,
	linux-kernel@vger.kernel.org,
	dri-devel <dri-devel@lists.freedesktop.org>,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Subject: Re: [PATCH 0/4] Add support for Hyperlinks and Markup on kernel-doc
Date: Fri, 14 Aug 2015 14:26:16 -0300	[thread overview]
Message-ID: <55CE24B8.5030508@collabora.co.uk> (raw)
In-Reply-To: <20150813172020.459bb599@xps.lwn.net>

On 08/13/2015 08:20 PM, Jonathan Corbet wrote:
> On Thu, 13 Aug 2015 20:09:35 -0300
> Danilo Cesar Lemes de Paula <danilo.cesar@collabora.co.uk> wrote:
> 
>> Did you find time to take a look on this?
> 
> No.  Just when I thought things couldn't get crazier, my laptop died.  
> 
> 	https://plus.google.com/+JonathanCorbet/posts/FBHp48dPb95
> 
> What spare time I had has been dedicated to recovering from that in time
> to give my talk next week.

Those evil machines... =)

>  
>> I understand that there's some discussion behind the curtains regarding
>> the markdown support, but the cross-reference-hyperlink patch is also in
>> the same patch series. It doesn't change any text in the docbook unless
>> there's really a cross-reference link to it. Different from the markdown
>> support (when people start to use markdown to write docs it will be hard
>> to go back), the cross-link stuff doesn't require/create any change to
>> current documentation, it is pretty safe to use.
>>
>> Would you mind to share your plans about this?
> 
> No behind-the-curtains discussions happening, or, let's say, if there
> are, I've not been invited either.

I meant the Kernel summit mailing list, but looks like that thread died
even before my patches.

> 
> I'd like to get back to the cross-reference stuff.  Last I tried, it
> failed while building the media docs; have you been able to look at
> that?  

I did, and I didn't find anything.
Media API already spits lots of warnings without my patch. I did send
those warnings to a file and count them. My patch produces the same
amount of warnings as the original branch.
I did, however, use a clean build to test that. Daniel Vetter complained
that the Documentation was being rebuilt all the time, something wrong
with the dependencies. I did fix that in v2. Maybe the errors you got
were related to it?


> 
> Longer term, as you may know from the kernel summit discussions, I'd
> really like to get rid of a lot of the XML gunk and put in something more
> straightforward, be it based on Markdown or something else.  Doing that,
> however, requires that I find the time to implement something that's
> convincingly better.  It may happen soon, but I sure can't guarantee it.
> 
> Meanwhile, I think it would be a horrible mistake to delay useful work
> because I have a gleam in my eye to do something different one of these
> years, so I'll not do that.  I fully expect to merge all of the stuff
> you've done, I just need to have a good look at it and test it out a
> bit.  As I said before, I can't promise that for the 4.3 merge window,
> but I'll try.
> 
> Apologies,

No need to apologize, just wanted to know what was going on.

Danilo Cesar
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

WARNING: multiple messages have this Message-ID (diff)
From: Danilo Cesar Lemes de Paula <danilo.cesar@collabora.co.uk>
To: Jonathan Corbet <corbet@lwn.net>
Cc: linux-doc@vger.kernel.org, Randy Dunlap <rdunlap@infradead.org>,
	Daniel Vetter <daniel.vetter@ffwll.ch>,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	Herbert Xu <herbert@gondor.apana.org.au>,
	Stephan Mueller <smueller@chronox.de>,
	Michal Marek <mmarek@suse.cz>,
	linux-kernel@vger.kernel.org,
	intel-gfx <intel-gfx@lists.freedesktop.org>,
	dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH 0/4] Add support for Hyperlinks and Markup on kernel-doc
Date: Fri, 14 Aug 2015 14:26:16 -0300	[thread overview]
Message-ID: <55CE24B8.5030508@collabora.co.uk> (raw)
In-Reply-To: <20150813172020.459bb599@xps.lwn.net>

On 08/13/2015 08:20 PM, Jonathan Corbet wrote:
> On Thu, 13 Aug 2015 20:09:35 -0300
> Danilo Cesar Lemes de Paula <danilo.cesar@collabora.co.uk> wrote:
> 
>> Did you find time to take a look on this?
> 
> No.  Just when I thought things couldn't get crazier, my laptop died.  
> 
> 	https://plus.google.com/+JonathanCorbet/posts/FBHp48dPb95
> 
> What spare time I had has been dedicated to recovering from that in time
> to give my talk next week.

Those evil machines... =)

>  
>> I understand that there's some discussion behind the curtains regarding
>> the markdown support, but the cross-reference-hyperlink patch is also in
>> the same patch series. It doesn't change any text in the docbook unless
>> there's really a cross-reference link to it. Different from the markdown
>> support (when people start to use markdown to write docs it will be hard
>> to go back), the cross-link stuff doesn't require/create any change to
>> current documentation, it is pretty safe to use.
>>
>> Would you mind to share your plans about this?
> 
> No behind-the-curtains discussions happening, or, let's say, if there
> are, I've not been invited either.

I meant the Kernel summit mailing list, but looks like that thread died
even before my patches.

> 
> I'd like to get back to the cross-reference stuff.  Last I tried, it
> failed while building the media docs; have you been able to look at
> that?  

I did, and I didn't find anything.
Media API already spits lots of warnings without my patch. I did send
those warnings to a file and count them. My patch produces the same
amount of warnings as the original branch.
I did, however, use a clean build to test that. Daniel Vetter complained
that the Documentation was being rebuilt all the time, something wrong
with the dependencies. I did fix that in v2. Maybe the errors you got
were related to it?


> 
> Longer term, as you may know from the kernel summit discussions, I'd
> really like to get rid of a lot of the XML gunk and put in something more
> straightforward, be it based on Markdown or something else.  Doing that,
> however, requires that I find the time to implement something that's
> convincingly better.  It may happen soon, but I sure can't guarantee it.
> 
> Meanwhile, I think it would be a horrible mistake to delay useful work
> because I have a gleam in my eye to do something different one of these
> years, so I'll not do that.  I fully expect to merge all of the stuff
> you've done, I just need to have a good look at it and test it out a
> bit.  As I said before, I can't promise that for the 4.3 merge window,
> but I'll try.
> 
> Apologies,

No need to apologize, just wanted to know what was going on.

Danilo Cesar

  reply	other threads:[~2015-08-14 17:26 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-23 18:16 [PATCH 0/4] Add support for Hyperlinks and Markup on kernel-doc Danilo Cesar Lemes de Paula
2015-07-23 18:16 ` [PATCH 1/4] scripts/kernel-doc: Adding cross-reference links to html documentation Danilo Cesar Lemes de Paula
2015-07-23 18:16 ` [PATCH 2/4] scripts/kernel-doc: Replacing highlights hash by an array Danilo Cesar Lemes de Paula
2015-07-23 18:16   ` Danilo Cesar Lemes de Paula
2015-07-23 18:16 ` [PATCH 3/4] scripts/kernel-doc: Adding infrastructure for markdown support Danilo Cesar Lemes de Paula
2015-07-23 18:16   ` Danilo Cesar Lemes de Paula
2015-07-23 18:16 ` [PATCH 4/4] drm/doc: Convert to markdown Danilo Cesar Lemes de Paula
2015-07-23 18:16   ` Danilo Cesar Lemes de Paula
2015-07-23 20:29 ` [PATCH 0/4] Add support for Hyperlinks and Markup on kernel-doc Jonathan Corbet
2015-08-13 23:09   ` Danilo Cesar Lemes de Paula
2015-08-13 23:20     ` Jonathan Corbet
2015-08-14 17:26       ` Danilo Cesar Lemes de Paula [this message]
2015-08-14 17:26         ` Danilo Cesar Lemes de Paula
2015-07-25 10:20 ` Stephan Mueller
2015-07-28 19:12   ` Danilo Cesar Lemes de Paula
2015-07-28 19:45 ` [PATCH v2 " Danilo Cesar Lemes de Paula
2015-07-28 19:45   ` [PATCH v2 1/4] scripts/kernel-doc: Adding cross-reference links to html documentation Danilo Cesar Lemes de Paula
2015-08-17  4:10     ` Jonathan Corbet
2015-08-17  4:10       ` Jonathan Corbet
2015-08-17 13:06       ` Danilo Cesar Lemes de Paula
2015-07-28 19:45   ` [PATCH v2 2/4] scripts/kernel-doc: Replacing highlights hash by an array Danilo Cesar Lemes de Paula
2015-07-28 19:45     ` Danilo Cesar Lemes de Paula
2015-11-17 10:40     ` Mauro Carvalho Chehab
2015-11-17 10:40       ` Mauro Carvalho Chehab
2015-11-17 14:44       ` Jonathan Corbet
2015-11-17 15:29         ` Mauro Carvalho Chehab
2015-11-17 15:48           ` Danilo Cesar Lemes de Paula
2015-11-17 15:48             ` Danilo Cesar Lemes de Paula
2015-11-18  0:21           ` Jonathan Corbet
2015-11-18  9:14             ` Mauro Carvalho Chehab
2015-11-18  9:14               ` Mauro Carvalho Chehab
2015-07-28 19:45   ` [PATCH v2 3/4] scripts/kernel-doc: Adding infrastructure for markdown support Danilo Cesar Lemes de Paula
2015-07-28 19:45     ` Danilo Cesar Lemes de Paula
2015-07-28 19:45   ` [PATCH v2 4/4] drm/doc: Convert to markdown Danilo Cesar Lemes de Paula
2015-07-28 19:45     ` Danilo Cesar Lemes de Paula

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=55CE24B8.5030508@collabora.co.uk \
    --to=danilo.cesar@collabora.co.uk \
    --cc=corbet@lwn.net \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=herbert@gondor.apana.org.au \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mmarek@suse.cz \
    --cc=rdunlap@infradead.org \
    --cc=smueller@chronox.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 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.