All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: "openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>,
	Alexander Kanavin <alex@linutronix.de>
Subject: RE: [OE-core] [PATCH 1/6] scripts/oe-setup-builddir: make it known where configurations come from
Date: Sat, 30 Jul 2022 09:54:59 +0000	[thread overview]
Message-ID: <33ed623c9f5147fea346548754ec498c@axis.com> (raw)
In-Reply-To: <CANNYZj9xE8EUR385HAy5BPcsiL8G_LPwaY9Q3GAXBp7sv45t4g@mail.gmail.com>

> -----Original Message-----
> From: Alexander Kanavin <alex.kanavin@gmail.com>
> Sent: den 29 juli 2022 22:12
> To: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
> Cc: openembedded-core@lists.openembedded.org; Alexander Kanavin
> <alex@linutronix.de>
> Subject: Re: [OE-core] [PATCH 1/6] scripts/oe-setup-builddir: make it
> known where configurations come from
> 
> On Fri, 29 Jul 2022 at 21:55, Peter Kjellerstedt <peter.kjellerstedt@axis.com> 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 are commented.
> >
> > or:
> >
> > You may wish to edit it to, e.g., select a different MACHINE (target hardware).
> > See conf/local.conf for more information as common configuration options are
> > commented.
> 
> I can do that, but I'm curious about this 80 character limit. Who
> cares, in 2022, and why?
> 
> Alex

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. ;)

//Peter



  reply	other threads:[~2022-07-30  9:55 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-29 14:10 [PATCH 1/6] scripts/oe-setup-builddir: make it known where configurations come from Alexander Kanavin
2022-07-29 14:10 ` [PATCH 2/6] bitbake-layers: add a command to save the active build configuration as a template into a layer Alexander Kanavin
2022-07-29 14:10 ` [PATCH 3/6] meta/files: add layer setup JSON schema and example Alexander Kanavin
2022-07-29 14:10 ` [PATCH 4/6] bitbake-layers: add ability to save current layer repository configuration into a json file Alexander Kanavin
2022-07-29 14:10 ` [PATCH 5/6] scripts/oe-setup-layers: add a script that restores the layer configuration from " Alexander Kanavin
2022-08-02 13:12   ` [OE-core] " Luca Ceresoli
2022-08-02 14:31     ` Alexander Kanavin
2022-07-29 14:10 ` [PATCH 6/6] selftest/bblayers: add a test for creating a layer setup and using it to restore the layers Alexander Kanavin
2022-08-16 20:29   ` [OE-core] " Richard Purdie
2022-08-16 20:41     ` Alexander Kanavin
2022-07-29 19:55 ` [OE-core] [PATCH 1/6] scripts/oe-setup-builddir: make it known where configurations come from Peter Kjellerstedt
2022-07-29 20:11   ` Alexander Kanavin
2022-07-30  9:54     ` Peter Kjellerstedt [this message]
2022-07-30 17:31       ` Alexander Kanavin
2022-07-30 18:15     ` Chuck Wolber

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=33ed623c9f5147fea346548754ec498c@axis.com \
    --to=peter.kjellerstedt@axis.com \
    --cc=alex.kanavin@gmail.com \
    --cc=alex@linutronix.de \
    --cc=openembedded-core@lists.openembedded.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 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.