From: Patrick Williams <patrick@stwcx.xyz>
To: Supreeth Venkatesh <supreeth.venkatesh@amd.com>
Cc: Lei Yu <yulei.sh@bytedance.com>, Michael Shen <gpgpgp@google.com>,
openbmc <openbmc@lists.ozlabs.org>,
dhruvaraj S <dhruvaraj@gmail.com>,
Brad Bishop <bradleyb@fuzziesquirrel.com>,
Ed Tanous <ed@tanous.net>,
Abinaya.Dhandapani@amd.com
Subject: Re: [RFC] BMC RAS Feature
Date: Mon, 3 Apr 2023 06:44:54 -0500 [thread overview]
Message-ID: <ZCq8NrJdaT7UTd8J@heinlein.vulture-banana.ts.net> (raw)
In-Reply-To: <d9f7b650-2e8b-7bd0-2125-035531ce549c@amd.com>
[-- Attachment #1: Type: text/plain, Size: 892 bytes --]
On Wed, Mar 22, 2023 at 07:07:24PM -0500, Supreeth Venkatesh wrote:
> Can someone please help create bmc-ras or amd-debug-collector repository
> as there are instances of openpower-debug-collector repository used for
> Open Power systems?
The typical process for requesting a new repository is to open an issue
to the TOF:
https://github.com/openbmc/technical-oversight-forum/issues
Ideally you would submit a refreshed version of your design into the
Docs repository, as one of the questions the TOF will likely have is
"what is the proposed design for this repository". You will also need
to have a list of who you expect to be the maintainers (OWNERS) of this
repository.
There have been a few other issues requesting new repositories in the
last year. You might want to read those for examples of the kinds of
discussion to expect.
--
Patrick Williams
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-04-03 11:51 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-21 5:14 [RFC] BMC RAS Feature Supreeth Venkatesh
2023-03-21 10:40 ` Patrick Williams
2023-03-21 15:07 ` Supreeth Venkatesh
2023-03-21 16:26 ` dhruvaraj S
2023-03-21 17:25 ` Supreeth Venkatesh
2023-03-22 7:10 ` Lei Yu
2023-03-23 0:07 ` Supreeth Venkatesh
2023-04-03 11:44 ` Patrick Williams [this message]
2023-04-03 16:32 ` Supreeth Venkatesh
[not found] ` <d65937a46b6fb4f9f94edbdef44af58e@imap.linux.ibm.com>
2023-04-03 16:36 ` Supreeth Venkatesh
2023-07-21 10:29 ` J Dhanasekar
2023-07-21 14:03 ` Venkatesh, Supreeth
2023-07-24 13:04 ` J Dhanasekar
2023-07-24 14:14 ` Venkatesh, Supreeth
2023-07-25 13:09 ` J Dhanasekar
2023-07-25 14:02 ` Venkatesh, Supreeth
2023-07-27 10:20 ` J Dhanasekar
2023-07-14 22:05 ` Bills, Jason M
2023-07-15 9:01 ` dhruvaraj S
2023-07-24 14:29 ` Venkatesh, Supreeth
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=ZCq8NrJdaT7UTd8J@heinlein.vulture-banana.ts.net \
--to=patrick@stwcx.xyz \
--cc=Abinaya.Dhandapani@amd.com \
--cc=bradleyb@fuzziesquirrel.com \
--cc=dhruvaraj@gmail.com \
--cc=ed@tanous.net \
--cc=gpgpgp@google.com \
--cc=openbmc@lists.ozlabs.org \
--cc=supreeth.venkatesh@amd.com \
--cc=yulei.sh@bytedance.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.