docs.lists.yoctoproject.org archive mirror
 help / color / mirror / Atom feed
From: "Quentin Schulz" <quentin.schulz@theobroma-systems.com>
To: Michael Opdenacker <michael.opdenacker@bootlin.com>
Cc: docs@lists.yoctoproject.org
Subject: Re: [docs] [PATCH] dev-manual: explicit that devpyshell is a task
Date: Tue, 31 Aug 2021 10:12:45 +0200	[thread overview]
Message-ID: <20210831081245.o5od4ngeoepl2sww@fedora> (raw)
In-Reply-To: <20210830141750.66210-1-michael.opdenacker@bootlin.com>

Hi Michael,

On Mon, Aug 30, 2021 at 04:17:50PM +0200, Michael Opdenacker wrote:
> Without this, readers could think that "devpyshell" is a script,
> at least until they read the remainder of the section.
> 
> Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com>

Reviewed-by: Quentin Schulz <foss@0leil.net>

Thanks!
Quentin

> ---
>  documentation/dev-manual/common-tasks.rst | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/documentation/dev-manual/common-tasks.rst b/documentation/dev-manual/common-tasks.rst
> index f3b5084436..6df1f3b791 100644
> --- a/documentation/dev-manual/common-tasks.rst
> +++ b/documentation/dev-manual/common-tasks.rst
> @@ -3476,7 +3476,7 @@ Similar to working within a development shell as described in the
>  previous section, you can also spawn and work within an interactive
>  Python development shell. When debugging certain commands or even when
>  just editing packages, ``devpyshell`` can be a useful tool. When you
> -invoke ``devpyshell``, all tasks up to and including
> +invoke the ``devpyshell`` task, all tasks up to and including
>  :ref:`ref-tasks-patch` are run for the
>  specified target. Then a new terminal is opened. Additionally, key
>  Python objects and code are available in the same way they are to
> -- 
> 2.25.1
> 

> 
> 
> 


  reply	other threads:[~2021-08-31  8:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-30 14:17 [PATCH] dev-manual: explicit that devpyshell is a task Michael Opdenacker
2021-08-31  8:12 ` Quentin Schulz [this message]
2021-08-31 17:24   ` [docs] " Michael Opdenacker

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=20210831081245.o5od4ngeoepl2sww@fedora \
    --to=quentin.schulz@theobroma-systems.com \
    --cc=docs@lists.yoctoproject.org \
    --cc=michael.opdenacker@bootlin.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).