From: "Trevor Woerner" <twoerner@gmail.com>
To: Mark Morton <Mark.Morton@windriver.com>
Cc: docs@lists.yoctoproject.org
Subject: Re: [docs] [PATCH] Fixed PDF build issue caused by duplicate IDs
Date: Wed, 24 Jun 2020 22:22:22 -0400 [thread overview]
Message-ID: <20200625022222.GA33261@linux-uys3> (raw)
In-Reply-To: <20200624235352.18790-1-mark.morton@windriver.com>
works for me!
On Wed 2020-06-24 @ 04:53:52 PM, Mark Morton wrote:
> Signed-off-by: Mark Morton <mark.morton@windriver.com>
Tested-by: Trevor Woerner <twoerner@gmail.com>
> ---
> documentation/test-manual/test-manual-test-process.xml | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/documentation/test-manual/test-manual-test-process.xml b/documentation/test-manual/test-manual-test-process.xml
> index 6e2157c62..15bf420a0 100644
> --- a/documentation/test-manual/test-manual-test-process.xml
> +++ b/documentation/test-manual/test-manual-test-process.xml
> @@ -1,7 +1,6 @@
> <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
> "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"
> [<!ENTITY % poky SYSTEM "../poky.ent"> %poky; ] >
> -<!--SPDX-License-Identifier: CC-BY-2.0-UK-->
>
> <chapter id='test-manual-test-process'>
>
> @@ -46,7 +45,7 @@
> The full build includes all these things and is slower but more comprehensive.</para>
> </section>
>
> - <section id='test-yocto-project-autobuilder-overview'>
> + <section id='test-release-builds'>
> <title>Release Builds</title>
>
> <para>The project typically has two major releases a year with a six month cadence in April
> --
> 2.17.1
>
>
prev parent reply other threads:[~2020-06-25 2:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-24 23:53 [PATCH] Fixed PDF build issue caused by duplicate IDs Mark Morton
2020-06-25 2:22 ` Trevor Woerner [this message]
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=20200625022222.GA33261@linux-uys3 \
--to=twoerner@gmail.com \
--cc=Mark.Morton@windriver.com \
--cc=docs@lists.yoctoproject.org \
/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