From: Thang Nguyen <thang@os.amperecomputing.com>
To: Nancy Yuen <yuenn@google.com>
Cc: OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: Re: Any convention on putting source codes into openbmc/openbmc repository
Date: Thu, 18 Feb 2021 08:31:21 +0700 [thread overview]
Message-ID: <42403202-49c9-2b85-1207-4c84ec491332@os.amperecomputing.com> (raw)
In-Reply-To: <CADfYTpF9yX0xheCwu5mftWs9b4YAe=ttGNNsf7GL8KkpW4dAcw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1520 bytes --]
On 18/02/2021 06:46, Nancy Yuen wrote:
> Code should be put into an appropriate repo, and repos created where
> necessary. Then referenced in recipes from openbmc/openbmc metalayers.
Thanks Nancy for the feedback. Do we have requirement for this or just a
recommendation?
>
> On Wed, Feb 17, 2021 at 12:55 AM Thang Nguyen
> <thang@os.amperecomputing.com <mailto:thang@os.amperecomputing.com>>
> wrote:
>
> Hi,
>
> We implemented several features using c/cpp codes. Currently we
> put the
> c/cpp source into the openbmc repository like below:
>
> https://github.com/ampere-openbmc/openbmc/tree/ampere/meta-ampere/meta-common/recipes-ac01/host/ampere-host-error-monitor
> <https://github.com/ampere-openbmc/openbmc/tree/ampere/meta-ampere/meta-common/recipes-ac01/host/ampere-host-error-monitor>
>
> https://github.com/ampere-openbmc/openbmc/tree/ampere/meta-ampere/meta-jade/recipes-ampere/host/ampere-scp-failover
> <https://github.com/ampere-openbmc/openbmc/tree/ampere/meta-ampere/meta-jade/recipes-ampere/host/ampere-scp-failover>
>
> I check from http://github.com/openbmc/openbmc
> <http://github.com/openbmc/openbmc> but don't see source
> codes put there. Is there any rule that prevent source codes put into
> the openbmc repository?
>
>
> Best Regards,
>
> Thang Q. Nguyen -
>
>
>
> --
>
> Nancy Yuen
>
>
>
> •
>
>
>
> Google Platforms
>
>
>
> •
>
>
>
> yuenn@google.com <mailto:yuenn@google.com>
>
>
>
> •
>
>
>
> Google LLC
>
[-- Attachment #2: Type: text/html, Size: 6644 bytes --]
next prev parent reply other threads:[~2021-02-18 1:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-17 8:54 Any convention on putting source codes into openbmc/openbmc repository Thang Nguyen
2021-02-17 23:46 ` Nancy Yuen
2021-02-18 1:31 ` Thang Nguyen [this message]
2021-02-18 5:23 ` Joel Stanley
2021-02-18 7:42 ` Thang Nguyen
2021-02-20 17:04 ` Patrick Williams
2021-02-22 8:25 ` Thang Nguyen
2021-02-22 14:26 ` Andrew Geissler
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=42403202-49c9-2b85-1207-4c84ec491332@os.amperecomputing.com \
--to=thang@os.amperecomputing.com \
--cc=openbmc@lists.ozlabs.org \
--cc=yuenn@google.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).