All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Tony Lee (李文富)" <Tony.Lee@quantatw.com>
To: "bradleyb@fuzziesquirrel.com" <bradleyb@fuzziesquirrel.com>
Cc: "openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>
Subject: RE: How to upload proposal and code for specifying and customizing projects?
Date: Wed, 6 Mar 2019 09:47:02 +0000	[thread overview]
Message-ID: <68bb4c4e34d94cd0b34016f178053799@quantatw.com> (raw)

Hi Brad,

I apologize for the confusion in previous mail.
Could you help create a repository for Quanta specific dbus interfaces, named "quanta-dbus-interfaces"?

Thanks
Best Regards,
Tony

-----Original Message-----
From: Tony Lee (李文富) 
Sent: Tuesday, March 5, 2019 3:06 PM
To: 'bradleyb@fuzziesquirrel.com' <bradleyb@fuzziesquirrel.com>
Cc: openbmc@lists.ozlabs.org
Subject: How to upload proposal and code for specifying and customizing projects?

Hi Brad,

I have two new packages "phosphor-nvme" and "quanta-dbus-interfaces" for specifying and customizing projects.
There was a service pooling status of NVMe devices in " phosphor-nvme " and several d-bus interfaces for Quanta in "quanta-dbus-interfaces".
 
1. Is it will be put into a new repository or put it under the meta-quanta?
2. As for the proposal, is it still need to commit to gerrit under openbmc/docs ?

Thanks
Best Regards,
Tony


             reply	other threads:[~2019-03-06  9:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-06  9:47 Tony Lee (李文富) [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-03-05  7:05 How to upload proposal and code for specifying and customizing projects? Tony Lee (李文富)
2019-03-07  4:19 ` Brad Bishop
2019-03-08  2:49   ` Tony Lee (李文富)
2019-03-08 17:34     ` Ed Tanous
2019-03-09  8:11       ` Tony Lee (李文富)
2019-03-11 17:45         ` Ed Tanous

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=68bb4c4e34d94cd0b34016f178053799@quantatw.com \
    --to=tony.lee@quantatw.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 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.