Em Fri, 1 Jul 2016 16:07:47 +0200
Markus Heiser escreveu:
> Am 01.07.2016 um 15:09 schrieb Jani Nikula :
>
> > On Fri, 01 Jul 2016, Markus Heiser wrote:
> >> In Sphinx, the code-block directive is a literal block, no refs or markup
> >> will be interpreted. This is different to what you know
On Fri, 01 Jul 2016, Mauro Carvalho Chehab wrote:
> Em Fri, 01 Jul 2016 20:24:48 +0300
> Jani Nikula escreveu:
>> The current media DocBook docs are a prime example. There are really
>> great features there, but IMHO done in a really complicated way and
>> specifically for media documentation (so
Em Fri, 01 Jul 2016 20:24:48 +0300
Jani Nikula escreveu:
> On Fri, 01 Jul 2016, Markus Heiser wrote:
> > Am 01.07.2016 um 14:58 schrieb Jonathan Corbet :
> >
> >> On Fri, 01 Jul 2016 13:44:17 +0300
> >> Jani Nikula wrote:
> >>
> >>> This is also one of the reasons why I so much want to kee
On Fri, 01 Jul 2016, Markus Heiser wrote:
> Am 01.07.2016 um 14:58 schrieb Jonathan Corbet :
>
>> On Fri, 01 Jul 2016 13:44:17 +0300
>> Jani Nikula wrote:
>>
>>> This is also one of the reasons why I so much want to keep everything
>>> behind one configuration file, and build everything in the S
Em Fri, 1 Jul 2016 16:07:47 +0200
Markus Heiser escreveu:
> Am 01.07.2016 um 15:09 schrieb Jani Nikula :
>
> > On Fri, 01 Jul 2016, Markus Heiser wrote:
> >> In Sphinx, the code-block directive is a literal block, no refs or markup
> >> will be interpreted. This is different to what you know
Em Fri, 1 Jul 2016 16:07:47 +0200
Markus Heiser escreveu:
> Am 01.07.2016 um 15:09 schrieb Jani Nikula :
>
> > On Fri, 01 Jul 2016, Markus Heiser wrote:
> >> In Sphinx, the code-block directive is a literal block, no refs or markup
> >> will be interpreted. This is different to what you know
Am 01.07.2016 um 14:58 schrieb Jonathan Corbet :
> On Fri, 01 Jul 2016 13:44:17 +0300
> Jani Nikula wrote:
>
>> This is also one of the reasons why I so much want to keep everything
>> behind one configuration file, and build everything in the Sphinx
>> toolchain. To keep it all more uniform, t
Am 01.07.2016 um 15:09 schrieb Jani Nikula :
> On Fri, 01 Jul 2016, Markus Heiser wrote:
>> In Sphinx, the code-block directive is a literal block, no refs or markup
>> will be interpreted. This is different to what you know from DocBook.
>> I will look for a solution, that matches your requirem
On Fri, 01 Jul 2016 13:44:17 +0300
Jani Nikula wrote:
> This is also one of the reasons why I so much want to keep everything
> behind one configuration file, and build everything in the Sphinx
> toolchain. To keep it all more uniform, to not duplicate stuff, and not
> deviate to some silos like
On Fri, 01 Jul 2016, Markus Heiser wrote:
> In Sphinx, the code-block directive is a literal block, no refs or markup
> will be interpreted. This is different to what you know from DocBook.
> I will look for a solution, that matches your requirement.
Parsed literal block solves the problem, but b
Em Fri, 01 Jul 2016 15:26:45 +0300
Jani Nikula escreveu:
> > In this example, the sphinx build is started as a side effect
> > even if it is not rebuild in this example, because nothing
> > in reST content has changed: "looking for now-outdated files... none found".
> >
> > As far as I can see, t
Em Fri, 1 Jul 2016 14:18:34 +0200
Markus Heiser escreveu:
> Am 01.07.2016 um 11:38 schrieb Mauro Carvalho Chehab
> :
>
>
> > Btw, yesterday, I tried to add references to a C code, at video.rst,
> > just like we did with DocBook:
> >
> > .. code-block:: c
> > :caption: Example 2: Switching t
Hi Jani,
Em Fri, 01 Jul 2016 13:44:17 +0300
Jani Nikula escreveu:
> On Fri, 01 Jul 2016, Mauro Carvalho Chehab wrote:
> > Not being able to compile just one docbook is a regression and breaks
> > my process. This needs to be fixed.
>
> Do you have a regression with *DocBook XML* on docs-next
On Fri, 01 Jul 2016, Markus Heiser wrote:
> Am 01.07.2016 um 13:56 schrieb Jani Nikula :
>
>> On Fri, 01 Jul 2016, Markus Heiser wrote:
>>> Am 01.07.2016 um 12:44 schrieb Jani Nikula :
>>>
On Fri, 01 Jul 2016, Mauro Carvalho Chehab wrote:
> Not being able to compile just one docbook is
On Thu, 30 Jun 2016, Mauro Carvalho Chehab wrote:
> Em Thu, 30 Jun 2016 13:05:11 -0600
> Jonathan Corbet escreveu:
>
>> Anyway, I don't want to delay this work, so I have gone ahead and applied
>> it;
>
> Got already one issue... Maybe on Jeni's changes to the makefiles...
>
> I want to be able
Am 01.07.2016 um 11:38 schrieb Mauro Carvalho Chehab :
> Btw, yesterday, I tried to add references to a C code, at video.rst,
> just like we did with DocBook:
>
> .. code-block:: c
> :caption: Example 2: Switching to the first video input
>
> int index;
>
> index = 0;
>
> if (-1 == i
Am 01.07.2016 um 13:56 schrieb Jani Nikula :
> On Fri, 01 Jul 2016, Markus Heiser wrote:
>> Am 01.07.2016 um 12:44 schrieb Jani Nikula :
>>
>>> On Fri, 01 Jul 2016, Mauro Carvalho Chehab wrote:
Not being able to compile just one docbook is a regression and breaks
my process. This nee
On Fri, 01 Jul 2016, Markus Heiser wrote:
> Am 01.07.2016 um 12:44 schrieb Jani Nikula :
>
>> On Fri, 01 Jul 2016, Mauro Carvalho Chehab wrote:
>>> Not being able to compile just one docbook is a regression and breaks
>>> my process. This needs to be fixed.
>>
>> Do you have a regression with *D
Am 01.07.2016 um 12:44 schrieb Jani Nikula :
> On Fri, 01 Jul 2016, Mauro Carvalho Chehab wrote:
>> Not being able to compile just one docbook is a regression and breaks
>> my process. This needs to be fixed.
>
> Do you have a regression with *DocBook XML* on docs-next now? If yes,
> clearly th
On Fri, 01 Jul 2016, Mauro Carvalho Chehab wrote:
> Not being able to compile just one docbook is a regression and breaks
> my process. This needs to be fixed.
Do you have a regression with *DocBook XML* on docs-next now? If yes,
clearly that must be fixed ASAP.
As to Sphinx, I fear your DocBook
Em Fri, 01 Jul 2016 10:44:27 +0200
Markus Heiser escreveu:
> Am 30.06.2016 um 21:44 schrieb Mauro Carvalho Chehab
> :
>
> > Em Thu, 30 Jun 2016 13:05:11 -0600
> > Jonathan Corbet escreveu:
> >
> >> Anyway, I don't want to delay this work, so I have gone ahead and applied
> >> it;
> >
>
Am 30.06.2016 um 21:44 schrieb Mauro Carvalho Chehab :
> Em Thu, 30 Jun 2016 13:05:11 -0600
> Jonathan Corbet escreveu:
>
>> Anyway, I don't want to delay this work, so I have gone ahead and applied
>> it;
>
> Got already one issue... Maybe on Jeni's changes to the makefiles...
>
> I want to
Am 30.06.2016 um 21:05 schrieb Jonathan Corbet :
> On Thu, 30 Jun 2016 14:00:21 +0200
> Markus Heiser wrote:
>
>> this is my flat-table patch on top of your docs-next branch / we discussed on
>> the ML
>
> Hmm... we don't have an official kernel coding style for Python, but if
> we did, I'd s
Em Thu, 30 Jun 2016 13:05:11 -0600
Jonathan Corbet escreveu:
> Anyway, I don't want to delay this work, so I have gone ahead and applied
> it;
Got already one issue... Maybe on Jeni's changes to the makefiles...
I want to be able to compile just the book I'm working. Using the usual
syntax to
Hi Markus/Jon,
Em Thu, 30 Jun 2016 13:05:11 -0600
Jonathan Corbet escreveu:
> On Thu, 30 Jun 2016 14:00:21 +0200
> Markus Heiser wrote:
>
> > this is my flat-table patch on top of your docs-next branch / we discussed
> > on
> > the ML
>
> Hmm... we don't have an official kernel coding st
On Thu, 30 Jun 2016 14:00:21 +0200
Markus Heiser wrote:
> this is my flat-table patch on top of your docs-next branch / we discussed on
> the ML
Hmm... we don't have an official kernel coding style for Python, but if
we did, I'd sure like it to be a lot more like the usual Python
conventions.
26 matches
Mail list logo
