Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Marcus Hoffmann <buildroot@bubu1.eu>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 2/6] utils/readme.txt: document docker-run script
Date: Tue, 6 Feb 2024 17:00:15 +0100	[thread overview]
Message-ID: <ZcJXjxMVP8i1fma4@landeda> (raw)
In-Reply-To: <20240206105246.1220945-2-buildroot@bubu1.eu>

Marcus, All,

On 2024-02-06 11:52 +0100, Marcus Hoffmann via buildroot spake thusly:
> Signed-off-by: Marcus Hoffmann <buildroot@bubu1.eu>
> ---
>  utils/readme.txt | 4 ++++
>  1 file changed, 4 insertions(+)
> 
> diff --git a/utils/readme.txt b/utils/readme.txt
> index d5cda70bfc..2cb6b0af9b 100644
> --- a/utils/readme.txt
> +++ b/utils/readme.txt
> @@ -18,6 +18,10 @@ check-package
>      It checks the .checkpackageignore file if errors should be ignored and
>      errors if there's a file listed that doesn't produce an error.
>  
> +docker-run
> +    a script that runs a command (like make check-package) inside the buildroot
> +    ci docker container.

I've slightly extended that to state that an interactive shell is
spawned if not command is specified.

Applied to master, thanks.

Regards,
Yann E. MORIN.

>  genrandconfig
>      a script that generates a random configuration, used by the autobuilders
>      (http://autobuild.buildroot.org). It selects a random toolchain from
> -- 
> 2.43.0
> 
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 561 099 427 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2024-02-06 16:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-06 10:52 [Buildroot] [PATCH 1/6] utils/readme.txt: expand check-package description Marcus Hoffmann via buildroot
2024-02-06 10:52 ` [Buildroot] [PATCH 2/6] utils/readme.txt: document docker-run script Marcus Hoffmann via buildroot
2024-02-06 16:00   ` Yann E. MORIN [this message]
2024-02-06 10:52 ` [Buildroot] [PATCH 3/6] docs/website/support.html: document how to join irc channel from matrix Marcus Hoffmann via buildroot
2024-02-06 16:00   ` Yann E. MORIN
2024-02-06 10:52 ` [Buildroot] [PATCH 4/6] docs/website/support.html: document irc channel permission changes Marcus Hoffmann via buildroot
2024-02-06 16:02   ` Yann E. MORIN
2024-02-06 10:52 ` [Buildroot] [PATCH 5/6] docs/manual/contribute.adoc: link to git-send-email.io Marcus Hoffmann via buildroot
2024-02-06 16:03   ` Yann E. MORIN
2024-02-06 10:52 ` [Buildroot] [PATCH 6/6] docs/manual/contribute.adoc: mention sr.ht as an alternative for sending patches Marcus Hoffmann via buildroot
2024-02-06 17:06   ` Yann E. MORIN
2024-02-06 15:59 ` [Buildroot] [PATCH 1/6] utils/readme.txt: expand check-package description Yann E. MORIN

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=ZcJXjxMVP8i1fma4@landeda \
    --to=yann.morin.1998@free.fr \
    --cc=buildroot@bubu1.eu \
    --cc=buildroot@buildroot.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