All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Garrett, Mike (HPE Server Firmware)" <mike.garrett@hpe.com>
To: Brad Bishop <bradleyb@fuzziesquirrel.com>,
	"Verdun, Jean-Marie" <jean-marie.verdun@hpe.com>,
	"openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>
Cc: "Shaffer, Scott" <scott.shaffer@hpe.com>,
	"Cisneros, Jorge (George)" <jorge.cisneros@hpe.com>,
	"Rodgers, Renee" <renee.rodgers@hpe.com>,
	"Chung, John (TWN iLO)" <john.chung@hpe.com>,
	"Chen, Gilbert" <gilbert.chen@hpe.com>,
	"Newman, Edward (iLO Firmware)" <edward.newman@hpe.com>
Subject: OpenBMC - how best to do meta-hpe commit
Date: Fri, 19 Jun 2020 15:37:34 +0000	[thread overview]
Message-ID: <DF4PR8401MB11459191B8F682B8DAB4707A8F980@DF4PR8401MB1145.NAMPRD84.PROD.OUTLOOK.COM> (raw)

Hi Brad and all,

Thank you for creating meta-hpe.  I'd like your opinion on the best way to do our initial meta-hpe commit.  Its currently 168 files split into (1) a machine layer for our DL360, (2) a BMC SOC layer, (3) a common layer for elements common to HPE platforms.  I know the team prefers small commits but would like your thoughts on this since it is more or less atomic.

I assume this would get committed to https://gerrit.openbmc-project.xyz/openbmc/meta-hpe and go through the normal Gerrit review process right?  I've looked and not been able to find good examples of other "1st commits" to see how it's been done in the past.

Thanks,

Mike

             reply	other threads:[~2020-06-19 16:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-19 15:37 Garrett, Mike (HPE Server Firmware) [this message]
2020-06-22  0:16 ` OpenBMC - how best to do meta-hpe commit Andrew Jeffery
2020-06-22 15:54 ` Brad Bishop

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=DF4PR8401MB11459191B8F682B8DAB4707A8F980@DF4PR8401MB1145.NAMPRD84.PROD.OUTLOOK.COM \
    --to=mike.garrett@hpe.com \
    --cc=bradleyb@fuzziesquirrel.com \
    --cc=edward.newman@hpe.com \
    --cc=gilbert.chen@hpe.com \
    --cc=jean-marie.verdun@hpe.com \
    --cc=john.chung@hpe.com \
    --cc=jorge.cisneros@hpe.com \
    --cc=openbmc@lists.ozlabs.org \
    --cc=renee.rodgers@hpe.com \
    --cc=scott.shaffer@hpe.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.