From: Zhihang Wei <wzh@ilbers.de>
To: Clara Kowalsky <clara.kowalsky@siemens.com>, isar-users@googlegroups.com
Subject: Re: [PATCH] docs: Refactor kas/README.md
Date: Fri, 6 Feb 2026 17:01:11 +0100 [thread overview]
Message-ID: <b0f00e9b-5209-4147-8806-e047ffc2371a@ilbers.de> (raw)
In-Reply-To: <20260204162959.823307-1-clara.kowalsky@siemens.com>
Applied to next, thanks.
Zhihang
On 2/4/26 17:29, 'Clara Kowalsky' via isar-users wrote:
> Fix some typos.
>
> Signed-off-by: Clara Kowalsky <clara.kowalsky@siemens.com>
> ---
> kas/README.md | 22 +++++++++++-----------
> 1 file changed, 11 insertions(+), 11 deletions(-)
>
> diff --git a/kas/README.md b/kas/README.md
> index d821f0c8..a54e4333 100644
> --- a/kas/README.md
> +++ b/kas/README.md
> @@ -1,14 +1,14 @@
> # Support of kas
>
> -[kas](https://github.com/siemens/kas) is a tool to setup bitbake based projects.
> +[kas](https://github.com/siemens/kas) is a tool to set up BitBake-based projects.
>
> -Directory `kas` contains required configuration fragments to setup and build
> -Isar with `kas-container` script and Kconfig language.
> +The `kas` directory contains the required configuration fragments to set up and build
> +Isar using the `kas-container` script and Kconfig language.
>
> ## Requirements
>
> -Since kas uses Docker or Podman based containers, users that runs Isar build
> -using `kas-container` script should be allowed to run these containers in
> +Since kas uses Docker or Podman based containers, users who run an Isar build
> +using the `kas-container` script should be allowed to run these containers in
> privileged mode.
>
> ## Configuring Isar build
> @@ -17,19 +17,19 @@ privileged mode.
> ./kas/kas-container menu
> ```
>
> -This creates `.config.yaml` file in isar root that stores the configuration.
> +This creates a `.config.yaml` file in the Isar root directory that stores the
> +configuration.
>
> -
> -## Building Isar after configuration done
> +## Building Isar after configuration is done
>
> ```
> ./kas/kas-container build
> ```
>
> -This generates `build/conf/` configuration and starts building Isar using
> -kas container. Required image will be downloaded if not yet).
> +This generates the `build/conf/` configuration and starts building Isar using
> +the kas container. The required image will be downloaded if not already present.
>
> -To access bulid shell, the following command can be used:
> +To access the build shell, the following command can be used:
>
> ```
> ./kas/kas-container shell
--
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/b0f00e9b-5209-4147-8806-e047ffc2371a%40ilbers.de.
prev parent reply other threads:[~2026-02-06 16:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-04 16:29 'Clara Kowalsky' via isar-users
2026-02-06 16:01 ` Zhihang Wei [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=b0f00e9b-5209-4147-8806-e047ffc2371a@ilbers.de \
--to=wzh@ilbers.de \
--cc=clara.kowalsky@siemens.com \
--cc=isar-users@googlegroups.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