All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Alexander Kanavin <alex.kanavin@gmail.com>,
	Martin Jansa <Martin.Jansa@gmail.com>,
	s.mueller-klieser@phytec.de, n.wesp@phytec.de
Cc: Rudolf J Streif <rudolf.streif@ibeeto.com>,
	Zoran <zoran.stojsavljevic@gmail.com>,
	Yocto-mailing-list <yocto@lists.yoctoproject.org>
Subject: Re: [yocto] LAYERSERIES_COMPAT_ variable in the layer's recipe
Date: Thu, 01 Dec 2022 10:41:42 +0000	[thread overview]
Message-ID: <7fb32274d35f9948a4962e9723f7eae684304c92.camel@linuxfoundation.org> (raw)
In-Reply-To: <CANNYZj8uXJ189UckEVktdEuRgLpAcn+driQqnxj0KLaGYSU=wQ@mail.gmail.com>

On Thu, 2022-12-01 at 11:09 +0100, Alexander Kanavin wrote:
> And this is the commit that did this:
> https://git.phytec.de/meta-phytec/commit/conf/layer.conf?id=8261e896d2b43211e7377feb38e919336d47c39f
> 
> Shame on you, phytec. Shame on you. What you do in your layers perhaps
> doesn't matter so much, but you also give everyone a bad example to
> follow.

That commit really is not in the spirit of things and I'm not happy
people are doing that. I'd not be surprised if that stopped working
soon.

We had a huge problem with unmaintained layers where it was unclear
which releases a master branch worked or had been tested with. An
actively maintained layer should have no problem with updating this a
couple of times a year. If that is an issue, it isn't actively
maintained and it makes that clear.

Cheers,

Richard


  reply	other threads:[~2022-12-01 10:41 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-01  4:27 LAYERSERIES_COMPAT_ variable in the layer's recipe Zoran Stojsavljevic
2022-12-01  6:06 ` [yocto] " Rudolf Streif
2022-12-01  7:46   ` Martin Jansa
2022-12-01 10:09     ` Alexander Kanavin
2022-12-01 10:41       ` Richard Purdie [this message]
2022-12-09 11:20       ` Stefan Müller-Klieser
2022-12-01 16:41     ` Rudolf J Streif
2022-12-01 17:01       ` Alexander Kanavin
2022-12-01 18:32         ` Zoran Stojsavljevic
2022-12-01 11:09 ` Ross Burton
2022-12-01 11:17   ` Martin Jansa
2022-12-01 12:46     ` Zoran Stojsavljevic
2022-12-01 12:48       ` Ross Burton
2022-12-01 13:01         ` Zoran Stojsavljevic
2022-12-01 12:38   ` Zoran Stojsavljevic

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=7fb32274d35f9948a4962e9723f7eae684304c92.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=Martin.Jansa@gmail.com \
    --cc=alex.kanavin@gmail.com \
    --cc=n.wesp@phytec.de \
    --cc=rudolf.streif@ibeeto.com \
    --cc=s.mueller-klieser@phytec.de \
    --cc=yocto@lists.yoctoproject.org \
    --cc=zoran.stojsavljevic@gmail.com \
    /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.