All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: Brandon Kim <brandonkim@google.com>
To: "OpenBMC (openbmc@lists.ozlabs.org)" <openbmc@lists.ozlabs.org>
Subject: Upstreaming downstream Google BMC repositories
Date: Wed, 6 Jan 2021 17:49:32 -0800	[thread overview]
Message-ID: <CALGRKGM0A9DHYuHrKrCLS8U0+YnbMCgVHWEXjbMW7Juhq+r=Zg@mail.gmail.com> (raw)

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

Hi everyone,

We're exploring ways of upstreaming some of the downstream repositories
from Google to openbmc/* .

Half, if not most of the downstream repositories are C++ daemons that are
specific to Google so we didn't want to create a bunch of new
openbmc/<repo> that no one would use.

An idea that Ed gave me was having something like openbmc/google-misc
repository for all these repositories and if there are any that seem useful
to others, we can break it out into a different, separate repository in
openbmc/* layer.

Please let me know if this seems like a good idea and I'm open to other
suggestions!

Thanks,
Brandon

[-- Attachment #2: Type: text/html, Size: 786 bytes --]

             reply	other threads:[~2021-01-07  1:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-07  1:49 Brandon Kim [this message]
2021-01-07  8:01 ` Upstreaming downstream Google BMC repositories Paul Menzel
2021-01-07 17:33   ` Benjamin Fair
2021-01-07 18:25     ` Paul Menzel
2021-01-07 21:20       ` Ed Tanous
2021-01-11 21:13         ` Patrick Williams
2021-01-11 21:51           ` Ed Tanous
2021-01-14 23:17             ` Brandon Kim
2021-01-20 19:04               ` Ed Tanous
2021-01-30 22:19               ` Brad Bishop
2021-01-30 22:23                 ` Ed Tanous
2021-02-01  2:21                   ` Brandon Kim

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='CALGRKGM0A9DHYuHrKrCLS8U0+YnbMCgVHWEXjbMW7Juhq+r=Zg@mail.gmail.com' \
    --to=brandonkim@google.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.