lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Fri, 24 Jun 2016 07:40:47 -0300
From:	Mauro Carvalho Chehab <mchehab@....samsung.com>
To:	Markus Heiser <markus.heiser@...marit.de>
Cc:	Jani Nikula <jani.nikula@...el.com>,
	Daniel Vetter <daniel.vetter@...ll.ch>,
	Jonathan Corbet <corbet@....net>,
	Grant Likely <grant.likely@...retlab.ca>,
	Dan Allen <dan@...ndevise.io>,
	Russel Winder <russel@...der.org.uk>,
	Keith Packard <keithp@...thp.com>,
	LKML <linux-kernel@...r.kernel.org>, linux-doc@...r.kernel.org,
	Hans Verkuil <hverkuil@...all.nl>
Subject: Re: [PATCH 00/10] Documentation/Sphinx

Em Tue, 31 May 2016 12:16:25 +0200
Markus Heiser <markus.heiser@...marit.de> escreveu:

> Am 30.05.2016 um 23:23 schrieb Mauro Carvalho Chehab <mchehab@....samsung.com>:
> 
> > Em Mon, 30 May 2016 23:05:34 +0300
> > Jani Nikula <jani.nikula@...el.com> escreveu:
> >   
> >>> I worry a little bit in that reST will be only one more toolchain 
> >>> beside DocBook .. in the long term, kernel's documentation 
> >>> should get rid of all the DocBook artifacts and for this a more
> >>> comprehensive solution is needed.    
> >> 
> >> We agree on the end goal, eradicate DocBook. I must say that in my
> >> experiments, apart from the media docs, almost everything converts
> >> surprisingly nicely or IMO "good enough" with just the tmplcvt script in
> >> this series.  
> > 
> > With regards to media, my plan is to merge create a topic branch based
> > on Kernel 4.7-rc1 at:
> > 	https://git.linuxtv.org/media_tree.git/
> > 
> > As none of the Jani's patches seem to affect the media API docs, it
> > seems I don't need to merge back from Jon's -next branch.
> > 
> > There, I intend to add Markus patches with the conversion from the
> > DocBook to rst, plus the flat-table extension logic.
> > 
> > Then, I'll work to manually fix what's needed and I'll add the 
> > automation scripting logic that we have at the DocBook Makefile
> > to work with the new media rst files.
> > 
> > Lastly, once the job's done, I'll drop Documentation/DocBook/media.
> > 
> > Markus,
> > 
> > With that regards, could you please send the patches to me?  
> 
> Yes. What is your timeline ... is it OK if I send you a patch in the 
> next two weeks? ... first I wan't to finish my other work / I'am just
> back from holiday .. a lot of work to do :-o

Hi Markus,

I'm wanting to start working on it next week, if possible.

I created an experimental branch on my tree for such work, where
I'm merging from both Jon's doc-next tree and from media tree at:
	https://git.linuxtv.org//mchehab/experimental.git/log/?h=docs-next

Could you please rebase your work with the media DocBook and with
the flat-table support to be on the top of it?

Thanks!
Mauro

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ