"with some default values" isn't clear; if the user wants to change or
inspect the default values and their history, we should help them find
where they are. This becomes especially important when using template
configs other than poky's.
Signed-off-by: Alexander Kanavin
---
scripts/oe-setup-bui
1/6] scripts/oe-setup-builddir: make it known
> where configurations come from
>
> "with some default values" isn't clear; if the user wants to change or
> inspect the default values and their history, we should help them find
> where they are. This becomes especially import
On Fri, 29 Jul 2022 at 21:55, Peter Kjellerstedt
wrote:
> Please continue to limit the text to within 80 characters (as it was):
>
> You may wish to edit it to, for example, select a different MACHINE (target
> hardware). See conf/local.conf for more information as common configuration
> options a
> -Original Message-
> From: Alexander Kanavin
> Sent: den 29 juli 2022 22:12
> To: Peter Kjellerstedt
> Cc: openembedded-core@lists.openembedded.org; Alexander Kanavin
>
> Subject: Re: [OE-core] [PATCH 1/6] scripts/oe-setup-builddir: make it
> known where
On Sat, 30 Jul 2022 at 11:55, Peter Kjellerstedt
wrote:
> Well, I care since all my windows happen to be 80 characters wide (and I have
> a lot of them on my 4K monitor). And since I care and most don't, keeping the
> 80 character width should hopefully not be too much of a problem. ;)
On the oth
On Fri, Jul 29, 2022 at 13:12 Alexander Kanavin
wrote:
I can do that, but I'm curious about this 80 character limit. Who
> cares, in 2022, and why?
I care :)
Why? It is an expectation built into a lot of tools for one thing.
The git commit log is one notable example. Wrapping commit messages
