openbmc.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Brad Bishop <bradleyb@fuzziesquirrel.com>
To: "Thang Q. Nguyen" <thang@os.amperecomputing.com>
Cc: OpenBMC Maillist <openbmc@lists.ozlabs.org>, Lancelot.Kao@fii-usa.com
Subject: Re: create meta-ampere folder in openbmc repo
Date: Mon, 8 Feb 2021 17:12:22 -0500	[thread overview]
Message-ID: <20210208221222.42tgcozztspf3mru@thinkpad.fuzziesquirrel.com> (raw)
In-Reply-To: <53126da0-c452-7c64-c3d4-735f38e518d3@os.amperecomputing.com>

On Sat, Feb 06, 2021 at 11:42:54AM +0700, Thang Q. Nguyen wrote:
>Hi Brad,
>
>Sorry for asking for your help again. 

no problem.

>Currently, I just have +1 or +2 permission when submitting codes to 
>github.com/openbmc/openbmc/meta-ampere. I don't have permission for 
>Ok-To-Test and Code-Review-from-owners. Can you help check?

Is this the change?
https://gerrit.openbmc-project.xyz/c/openbmc/openbmc/+/40355

The submit button won't appear until the patch is verified. 

You should add yourself to ampere/ci-authorized to fix Ok-To-Test.

Please let me know if these suggestions don't resolve the problem.

thx - brad

  reply	other threads:[~2021-02-08 22:14 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
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 [this message]
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=20210208221222.42tgcozztspf3mru@thinkpad.fuzziesquirrel.com \
    --to=bradleyb@fuzziesquirrel.com \
    --cc=Lancelot.Kao@fii-usa.com \
    --cc=openbmc@lists.ozlabs.org \
    --cc=thang@os.amperecomputing.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 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).