On Mon, 7 Nov 2016 23:13:03 -0200
Mauro Carvalho Chehab wrote:
> Argh! PDF output is really fragile. I would change it then to:
>
> .. [#f1] You can, optionally, provide both good and bad arguments at git
>start: ``git bisect start [BAD] [GOOD]``
>
> Do you want me to write such patch o
Em Mon, 7 Nov 2016 17:39:02 -0700
Jonathan Corbet escreveu:
> On Mon, 7 Nov 2016 17:03:17 -0200
> Mauro Carvalho Chehab wrote:
>
> > +.. [#f1] You can, optionally, provide both good and bad arguments at git
> > +start::
> > +
> > + git bisect start [BAD] [GOOD]
>
> So this, as
Em Mon, 7 Nov 2016 16:55:26 -0700
Jonathan Corbet escreveu:
> On Mon, 7 Nov 2016 17:03:17 -0200
> Mauro Carvalho Chehab wrote:
>
> > Better organize the admin guide documentation by moving the
> > bug bisect to a separate file.
> >
> > Signed-off-by: Mauro Carvalho Chehab
> > ---
> > Docume
On Mon, 7 Nov 2016 17:03:17 -0200
Mauro Carvalho Chehab wrote:
> +.. [#f1] You can, optionally, provide both good and bad arguments at git
> + start::
> +
> + git bisect start [BAD] [GOOD]
So this, as it turns out, kills the PDF build:
Markup is unsupported in LaTeX:
admin-gui
On Mon, 7 Nov 2016 17:03:17 -0200
Mauro Carvalho Chehab wrote:
> Better organize the admin guide documentation by moving the
> bug bisect to a separate file.
>
> Signed-off-by: Mauro Carvalho Chehab
> ---
> Documentation/admin-guide/bug-bisect.rst | 78
> +++
> D
Better organize the admin guide documentation by moving the
bug bisect to a separate file.
Signed-off-by: Mauro Carvalho Chehab
---
Documentation/admin-guide/bug-bisect.rst | 78 +++
Documentation/admin-guide/bug-hunting.rst | 74 -
Docume
