All of lore.kernel.org
 help / color / mirror / Atom feed
From: Quentin Schulz <quentin.schulz@theobroma-systems.com>
To: Max Krummenacher <max.oss.09@gmail.com>, docs@lists.yoctoproject.org
Cc: Max Krummenacher <max.krummenacher@toradex.com>
Subject: Re: [docs] [PATCH] ref-manual: fix patch documentation
Date: Mon, 3 Jan 2022 12:53:41 +0100	[thread overview]
Message-ID: <21ea4b42-153a-c8d0-8e47-8a9e7f867174@theobroma-systems.com> (raw)
In-Reply-To: <20211228124602.3268-1-max.krummenacher@toradex.com>

Hi Max,

On 12/28/21 13:46, Max Krummenacher wrote:
> The do_patch implementation does not apply patches from an entry in
> SRC_URI pointing to a directory.
> Remove the claim that this is implemented.
> 
> Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
> ---
>   documentation/ref-manual/tasks.rst | 16 +++++++---------
>   1 file changed, 7 insertions(+), 9 deletions(-)
> 
> diff --git a/documentation/ref-manual/tasks.rst b/documentation/ref-manual/tasks.rst
> index 8d563714a..76f55e1ff 100644
> --- a/documentation/ref-manual/tasks.rst
> +++ b/documentation/ref-manual/tasks.rst
> @@ -326,21 +326,19 @@ file as a patch file::
>          file://file;apply=yes \
>          "
>   
> -Conversely, if you have a directory full of patch files and you want to
> -exclude some so that the ``do_patch`` task does not apply them during
> -the patch phase, you can use the "apply=no" parameter with the
> +Conversely, if you have a file ``*.patch`` and ``*.diff`` and you want

"""
Conversely, if you have a file whose file type is ``.patch`` or 
``.diff`` and you want to exclude it so
"""

to match the wording used for the apply=yes example just above the git 
context above.

> +that the ``do_patch`` task does not apply it during the patch phase,
> +you can use the "apply=no" parameter with the
>   :term:`SRC_URI` statement::
>   
>      SRC_URI = " \
>          git://path_to_repo/some_package \
> -       file://path_to_lots_of_patch_files \
> -       file://path_to_lots_of_patch_files/patch_file5;apply=no \
> +       file://file1.patch \
> +       file://file2.patch;apply=no \
>          "
>   
> -In the
> -previous example, assuming all the files in the directory holding the
> -patch files end with either ``.patch`` or ``.diff``, every file would be
> -applied as a patch by default except for the ``patch_file5`` patch.
> +In the previous example file1.patch would be applied as a patch by default
> +while file2.patch would not be applied.
>   

s/file1.patch/``file1.patch``/
s/file2.patch/``file2.patch``/

Cheers,
Quentin


      reply	other threads:[~2022-01-03 11:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-28 12:46 [PATCH] ref-manual: fix patch documentation Max Krummenacher
2022-01-03 11:53 ` Quentin Schulz [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=21ea4b42-153a-c8d0-8e47-8a9e7f867174@theobroma-systems.com \
    --to=quentin.schulz@theobroma-systems.com \
    --cc=docs@lists.yoctoproject.org \
    --cc=max.krummenacher@toradex.com \
    --cc=max.oss.09@gmail.com \
    /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.