All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Williams <patrick@stwcx.xyz>
To: "Thang Q. Nguyen" <thang@os.amperecomputing.com>
Cc: OpenBMC Maillist <openbmc@lists.ozlabs.org>,
	Brad Bishop <bradleyb@fuzziesquirrel.com>,
	Lancelot.Kao@fii-usa.com
Subject: Re: create meta-ampere folder in openbmc repo
Date: Sat, 30 Jan 2021 08:11:01 -0600	[thread overview]
Message-ID: <YBVo9es4vomuy7Iw@heinlein> (raw)
In-Reply-To: <96568613-294f-8a3b-9aa9-7918b5df2d9b@os.amperecomputing.com>

[-- Attachment #1: Type: text/plain, Size: 933 bytes --]

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:
> 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?
> 
> - Start from the beginning on openbmc/openbmc?

Brad said yesterday on Discord he was planning to push the existing
meta-ampere and meta-fii directly to the openbmc/openbmc tree[1] so it
would preserve their existing history.  I suspect you'll just need to wait
for him to do that, hopefully on Monday.  I don't think any of the
permissions exist on the subtrees (like meta-ampere) anymore, so even if
you push a commit there you won't be able to merge it.

1. https://discord.com/channels/775381525260664832/775694761775464468/804740846415118336

-- 
Patrick Williams

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2021-01-30 14:57 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 [this message]
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
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=YBVo9es4vomuy7Iw@heinlein \
    --to=patrick@stwcx.xyz \
    --cc=Lancelot.Kao@fii-usa.com \
    --cc=bradleyb@fuzziesquirrel.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 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.