From: "Thang Q. Nguyen" <thang@os.amperecomputing.com>
To: openbmc@lists.ozlabs.org
Subject: Re: Gerrit owners plugin coming
Date: Thu, 28 Jan 2021 09:06:02 +0700 [thread overview]
Message-ID: <5a209aef-f6cd-40fe-bd3b-8a4e1c623c8a@os.amperecomputing.com> (raw)
In-Reply-To: <CAH2-KxAC1r2tSOmbCyyvnYcY0Z-iyW97FoGHbtzitVNH1u5jow@mail.gmail.com>
On 1/28/21 00:09, Ed Tanous wrote:
> On Wed, Jan 27, 2021 at 4:02 AM Alexander Amelkin <a.amelkin@yadro.com> wrote:
>> 26.01.2021 00:26, Ed Tanous пишет:
>>> On Wed, Jan 20, 2021 at 11:23 AM Ed Tanous <ed@tanous.net> wrote:
>>>> Over the last few weeks, we've been slowly getting the gerrit owners
>>>> plugin deployed and tested, and got the OWNERS files merged into their
>>>> respective meta layers.
>>> These changes are live. Any commits to the individual meta layers can
>>> now be submitted directly to openbmc/openbmc now. If there's anything
>>> broken about the new workflow, or anything unexpected happens in your
>>> workflow, please let me know on discord and we'll try to get it
>>> resolved.
>> Does this mean that meta-<vendor> directories are not subtrees anymore
>> and respective repositories are now obsolete and can (will?) be dropped?
>>
> The intent was to make them read-only in case someone was relying on
> them directly.
Hi Ed,
Any problem with meta-* repos which have not been integrated into the
main openbmc repo? For example, meta-ampere, meta-fii.
And with the change, the new change will be submitted into
openbmc/openbmc repos in gerrit instead of openbmc/meta-*?
>> Thanks.
>>
>> Alexander.
>>
next prev parent reply other threads:[~2021-01-28 2:08 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
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 [this message]
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=5a209aef-f6cd-40fe-bd3b-8a4e1c623c8a@os.amperecomputing.com \
--to=thang@os.amperecomputing.com \
--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).