From: Uladzimir Bely <ubely@ilbers.de>
To: isar-users@googlegroups.com
Subject: Re: [PATCH 0/2] Updates in the documentation
Date: Tue, 06 Feb 2024 11:09:23 +0300 [thread overview]
Message-ID: <e09095778257c1c24598947f3f895f0488bd3c12.camel@ilbers.de> (raw)
In-Reply-To: <20240130101506.27451-1-ubely@ilbers.de>
On Tue, 2024-01-30 at 11:15 +0100, Uladzimir Bely wrote:
> Small polishes in the documentation files before upcoming
> release v0.10.
>
> If there are more things to update in the documentation files,
> they can be added to new versions of this patchset.
>
> Uladzimir Bely (2):
> doc/user_manual.md: Fix/update the contents
> image-account-extension: Move examples to user manual
>
> doc/user_manual.md | 32
> ++++++++++++++++++--
> meta/classes/image-account-extension.bbclass | 18 -----------
> 2 files changed, 30 insertions(+), 20 deletions(-)
>
> --
> 2.20.1
>
Applied to next.
prev parent reply other threads:[~2024-02-06 8:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-30 10:15 Uladzimir Bely
2024-01-30 10:15 ` [PATCH 1/2] doc/user_manual.md: Fix/update the contents Uladzimir Bely
2024-01-30 10:15 ` [PATCH 2/2] image-account-extension: Move examples to user manual Uladzimir Bely
2024-02-06 8:09 ` Uladzimir Bely [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=e09095778257c1c24598947f3f895f0488bd3c12.camel@ilbers.de \
--to=ubely@ilbers.de \
--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