openbmc.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Thang Q. Nguyen" <thang@os.amperecomputing.com>
To: Brad Bishop <bradleyb@fuzziesquirrel.com>
Cc: OpenBMC Maillist <openbmc@lists.ozlabs.org>, Lancelot.Kao@fii-usa.com
Subject: Re: create meta-ampere folder in openbmc repo
Date: Sun, 31 Jan 2021 07:56:30 +0700	[thread overview]
Message-ID: <ec320044-0898-0c0f-3e93-21bcadf49ffc@os.amperecomputing.com> (raw)
In-Reply-To: <20210130161537.gj6jhwvsnwgdkofa@thinkpad.fuzziesquirrel.com>


On 1/30/21 23:15, Brad Bishop wrote:
> On Sat, Jan 30, 2021 at 10:37:52AM +0700, Thang Q. Nguyen wrote:
>> On 1/5/21 20:54, Brad Bishop wrote:
>>> On Tue, 2021-01-05 at 08:48 +0700, Thang Q. Nguyen wrote:
>>>> Hi Brad,
>>>>
>>>> Just a reminder. Have you got any chance to check our meta-ampere?
>>> Hello Thang
>>>
>>> Apologies for the lack of responsiveness.  This is definitely on my 
>>> todo
>>> list, along with the request from Fii.
>>>
>>> thx - brad
>>>
>>
>> Hi Brad,
>>
>> With the change recently in owner plugin, what should I do with my 
>> meta-ampere?
>>
>> - Wait for meta-ampere integrated to openbmc/openbmc before pushing 
>> new codes?
>
> Hi Thang, I pushed the commits in meta-ampere to openbmc/openbmc just 
> now.  Going forward please submit meta-ampere patches to openbmc 
> instead of meta-ampere.  You'll want to submit an OWNERS file in 
> meta-ampere so that you can approve metadata in meta-ampere.
>
> This is long overdue, thanks for being patient.  Like I said in the 
> meta-fii note, thanks to the work of Ed, and others, to deploy the 
> owners plugin this shouldn't be a problem for others in the future.
>
> thx -brad

Thanks Brad for your great support.

I have just added the OWNER file into meta-ampere at 
https://gerrit.openbmc-project.xyz/c/openbmc/openbmc/+/40157.


  reply	other threads:[~2021-01-31  0:58 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-16  9:54 create meta-ampere folder in openbmc repo Thang Q. Nguyen
2020-12-24  1:46 ` Thang Q. Nguyen
2021-01-05  1:48   ` Thang Q. Nguyen
2021-01-05 13:54     ` Brad Bishop
2021-01-30  3:37       ` Thang Q. Nguyen
2021-01-30 14:11         ` Patrick Williams
2021-01-30 16:15         ` Brad Bishop
2021-01-31  0:56           ` Thang Q. Nguyen [this message]
2021-01-31  1:01           ` Thang Q. Nguyen
2021-02-01 13:48             ` Brad Bishop
2021-02-02  1:54               ` Thang Q. Nguyen
2021-02-06  4:42               ` Thang Q. Nguyen
2021-02-08 22:12                 ` Brad Bishop
2021-02-08 22:18                   ` Thang Nguyen OS
2021-02-08 22:27                     ` Brad Bishop
2021-02-08 22:48                       ` Thang Nguyen OS

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=ec320044-0898-0c0f-3e93-21bcadf49ffc@os.amperecomputing.com \
    --to=thang@os.amperecomputing.com \
    --cc=Lancelot.Kao@fii-usa.com \
    --cc=bradleyb@fuzziesquirrel.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).