From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Fiona Klute <fiona.klute@gmx.de>
Cc: Brandon Maier <Brandon.Maier@collins.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2] docs/manual: use space-separated list for BR2_EXTERNAL
Date: Wed, 4 Sep 2024 22:58:12 +0200 [thread overview]
Message-ID: <ZtjJ5PiY4fKcbl9m@landeda> (raw)
In-Reply-To: <b37f65c3-93c5-47ea-b7e6-bb542aa208e0@gmx.de>
Fiona, All,
On 2024-09-04 19:59 +0200, Fiona Klute via buildroot spake thusly:
> Am 04.09.24 um 12:07 schrieb Yann E. MORIN:
[--SNIP--]
> > Change the documentation to only mention using a space-separated list.
> > Of course, for backward compatibility, we keep the code as-is to accept
> > a colon-separated list, but we just do not advertise it.
> I think it might make sense to add a comment that explains this in
> support/scripts/br2-external where the colon substitution happens,
Good idea, I've done so in v3 that I just sent. Thanks for the review!
> to
> avoid confusing people who don't know the history.
"git log" will give you the history! ;-)
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| 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
prev parent reply other threads:[~2024-09-04 20:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-04 10:07 [Buildroot] [PATCH v2] docs/manual: use space-separated list for BR2_EXTERNAL Yann E. MORIN
2024-09-04 17:59 ` Fiona Klute via buildroot
2024-09-04 20:58 ` Yann E. MORIN [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=ZtjJ5PiY4fKcbl9m@landeda \
--to=yann.morin.1998@free.fr \
--cc=Brandon.Maier@collins.com \
--cc=buildroot@buildroot.org \
--cc=fiona.klute@gmx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.