mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: barebox@lists.infradead.org
Cc: Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: [PATCH 2/2] Documentation: user: versioning: reduce indentation
Date: Thu, 24 Apr 2025 13:06:31 +0200	[thread overview]
Message-ID: <20250424110631.3943702-2-a.fatoum@pengutronix.de> (raw)
In-Reply-To: <20250424110631.3943702-1-a.fatoum@pengutronix.de>

The bullet points are indented a lot, reduce them to normal.

Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
---
 Documentation/user/versioning.rst | 36 +++++++++++++++----------------
 1 file changed, 18 insertions(+), 18 deletions(-)

diff --git a/Documentation/user/versioning.rst b/Documentation/user/versioning.rst
index 0a8095a2e085..d8e2fdbc4574 100644
--- a/Documentation/user/versioning.rst
+++ b/Documentation/user/versioning.rst
@@ -7,15 +7,15 @@ In addition to the usual barebox release (e.g. ``v2025.03.0``), the
 version number can be extended to encode integration-specific version
 information:
 
-  * When built from git, ``scripts/setlocalversion`` will factor in
-    git revision information into the version string.
-  * The ``EXTRAVERSION =`` in the top-level ``Makefile`` can be used
-    to add a suffix to the version. This is useful if patches are applied
-    on top of the tarball release.
-  * The build host can set the ``BUILDSYSTEM_VERSION`` environment variable
-    prior to executing ``make`` to encode a board support package version.
-    This is useful to encode information about built-in environment
-    and firmware.
+* When built from git, ``scripts/setlocalversion`` will factor in
+  git revision information into the version string.
+* The ``EXTRAVERSION =`` in the top-level ``Makefile`` can be used
+  to add a suffix to the version. This is useful if patches are applied
+  on top of the tarball release.
+* The build host can set the ``BUILDSYSTEM_VERSION`` environment variable
+  prior to executing ``make`` to encode a board support package version.
+  This is useful to encode information about built-in environment
+  and firmware.
 
 Query from barebox
 ^^^^^^^^^^^^^^^^^^
@@ -32,17 +32,17 @@ Query from OS
 The barebox version (formatted as ``barebox-$version``) can be queried
 after boot by different means:
 
- * If the OS is booted with device tree, barebox will fixup a
-   ``/chosen/barebox-version`` property into the kernel device tree with
-   the version string. Under Linux, this can be accessed at:
+* If the OS is booted with device tree, barebox will fixup a
+  ``/chosen/barebox-version`` property into the kernel device tree with
+  the version string. Under Linux, this can be accessed at:
 
-   * ``/sys/firmware/devicetree/base/chosen/barebox-version``
-   * ``/proc/device-tree/base/chosen/barebox-version``
+ * ``/sys/firmware/devicetree/base/chosen/barebox-version``
+ * ``/proc/device-tree/base/chosen/barebox-version``
 
- * If the system is booted through barebox as EFI application (payload),
-   a ``LoaderInfo`` EFI variable with the systemd vendor GUID will
-   be set to the version string. Under Linux, the string is shown in
-   ``bootctl`` output
+* If the system is booted through barebox as EFI application (payload),
+  a ``LoaderInfo`` EFI variable with the systemd vendor GUID will
+  be set to the version string. Under Linux, the string is shown in
+  ``bootctl`` output
 
 Query without booting
 ^^^^^^^^^^^^^^^^^^^^^
-- 
2.39.5




      reply	other threads:[~2025-04-24 12:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-24 11:06 [PATCH 1/2] Documentation: user: versioning: fix formatting Ahmad Fatoum
2025-04-24 11:06 ` Ahmad Fatoum [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=20250424110631.3943702-2-a.fatoum@pengutronix.de \
    --to=a.fatoum@pengutronix.de \
    --cc=barebox@lists.infradead.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