public inbox for buildroot@busybox.net
 help / color / mirror / Atom feed
From: "Yann E. MORIN via buildroot" <buildroot@buildroot.org>
To: buildroot@buildroot.org
Cc: Arnout Vandecappelle <arnout@mind.be>,
	Brandon Maier <Brandon.Maier@collins.com>,
	Fiona Klute <fiona.klute@gmx.de>,
	"Yann E . MORIN" <yann.morin.1998@free.fr>
Subject: [Buildroot] [PATCH 0/3 v4] support/br2-external: fix shellcheck and better document BR2_EXTERNAL (branch yem/misc)
Date: Tue,  3 Feb 2026 22:54:23 +0100	[thread overview]
Message-ID: <cover.1770155657.git.yann.morin.1998@free.fr> (raw)

Hello All!

This small series is a respin of an old patch [0] that has been
lingering for quite some time now...

Baiscally, the case is to only document the fact that BR2_EXTERNAL is a
space-separated list, like all other lists in Buildroot, and not a
colon-separated one (but still support colon-separated lists for legacy
purposes).

As a bonus from the previous iterations, the series now cleans up
shelcheck errors in the script.

[0] https://patchwork.ozlabs.org/project/buildroot/patch/20240904205354.504964-1-yann.morin.1998@free.fr/

Changes v3 -> v4:
  - fix pre-existing shellcheck errors
  - extend commit log with more data

Changes v2 -> v3:
  - add comment in support/scripts/br2-external  (Fiona)

Changes v1 -> v2:
  - fix typoes

Regards,
Yann E. MORIN.


----------------------------------------------------------------
Yann E. MORIN (3):
      support/br2-external: remove leftover trap
      support/br2-external: fix remaining shellcheck errors
      docs/manual: use space-separated list for BR2_EXTERNAL

 .checkpackageignore                   |  1 -
 docs/manual/customize-outside-br.adoc |  5 +++--
 support/scripts/br2-external          | 20 ++++++++++++--------
 3 files changed, 15 insertions(+), 11 deletions(-)

--
.-----------------.--------------------.------------------.--------------------.
|  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:[~2026-02-03 21:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-03 21:54 Yann E. MORIN via buildroot [this message]
2026-02-03 21:54 ` [Buildroot] [PATCH 1/3 v4] support/br2-external: remove leftover trap Yann E. MORIN via buildroot
2026-03-13 21:25   ` Romain Naour via buildroot
2026-03-20 15:55   ` Thomas Perale via buildroot
2026-02-03 21:54 ` [Buildroot] [PATCH 2/3 v4] support/br2-external: fix remaining shellcheck errors Yann E. MORIN via buildroot
2026-03-20 15:55   ` Thomas Perale via buildroot
2026-02-03 21:54 ` [Buildroot] [PATCH 3/3 v4] docs/manual: use space-separated list for BR2_EXTERNAL Yann E. MORIN via buildroot
2026-03-20 15:55   ` Thomas Perale via buildroot

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=cover.1770155657.git.yann.morin.1998@free.fr \
    --to=buildroot@buildroot.org \
    --cc=Brandon.Maier@collins.com \
    --cc=arnout@mind.be \
    --cc=fiona.klute@gmx.de \
    --cc=yann.morin.1998@free.fr \
    /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