From: Andrew Geissler <geissonator@gmail.com>
To: Ed Tanous <ed@tanous.net>, Brad Bishop <bradleyb@fuzziesquirrel.com>
Cc: OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: Re: Gerrit owners plugin coming
Date: Thu, 21 Jan 2021 10:07:21 -0600 [thread overview]
Message-ID: <F55AAE75-B6DB-4185-95AB-4318E725B0C1@gmail.com> (raw)
In-Reply-To: <CACWQX821ADQCrekLj_bGAu=1SSLCv5pTee7jaoVo2Zs6havgnA@mail.gmail.com>
> On Jan 20, 2021, at 1:23 PM, Ed Tanous <ed@tanous.net> wrote:
>
>
> Overall, I hope that this will be a great improvement in the overall
> structure and usability of openbmc, and remove at least one stumbling
> block people new to the project tend to hit.
Thanks Ed, this is going to be great!
Brad, we run this autobump[1] script in a cron job right now. It scans the meta-* layer
recipes and creates bumps into the meta-* layers as needed. I assume all we
need to do is tweak this to just look at openbmc/openbmc meta-* layers now and
do the same bumps against openbmc/openbmc?
I’ll continue to utilize openbmc-config[2] for non-openbmc meta layers
(i.e. meta-openembedded,…) but no need to run against our openbmc
meta-* layers after this change.
Once we change over, I’ll also be disabling the meta-* layers CI job
(https://jenkins.openbmc.org/job/ci-meta/)
Andrew
[1]: https://github.com/openbmc/openbmc-tools/blob/master/openbmc-autobump/openbmc-autobump.py
[2]: https://github.com/bradbishop/openbmc-config
>
> -Ed
next prev parent reply other threads:[~2021-01-21 16:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-20 19:23 Gerrit owners plugin coming Ed Tanous
2021-01-20 23:20 ` Andrew Jeffery
2021-01-21 16:07 ` Andrew Geissler [this message]
2021-01-25 13:47 ` Brad Bishop
2021-01-25 13:49 ` Brad Bishop
2021-01-25 18:04 ` Klaus Heinrich Kiwi
2021-01-25 21:27 ` Ed Tanous
2021-01-25 21:26 ` Ed Tanous
2021-01-27 11:59 ` Alexander Amelkin
2021-01-27 17:09 ` Ed Tanous
2021-01-28 0:37 ` Brad Bishop
2021-01-28 2:06 ` Thang Q. Nguyen
2021-01-28 17:23 ` Ed Tanous
2021-01-29 2:09 ` Thang Q. Nguyen
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=F55AAE75-B6DB-4185-95AB-4318E725B0C1@gmail.com \
--to=geissonator@gmail.com \
--cc=bradleyb@fuzziesquirrel.com \
--cc=ed@tanous.net \
--cc=openbmc@lists.ozlabs.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).