From: Brandon Kim <brandonkim@google.com>
To: Ed Tanous <edtanous@google.com>
Cc: Paul Menzel <pmenzel@molgen.mpg.de>,
OpenBMC Maillist <openbmc@lists.ozlabs.org>,
Brad Bishop <bradleyb@fuzziesquirrel.com>,
Ed Tanous <ed@tanous.net>,
Benjamin Fair <benjaminfair@google.com>
Subject: Re: Upstreaming downstream Google BMC repositories
Date: Sun, 31 Jan 2021 18:21:59 -0800 [thread overview]
Message-ID: <CALGRKGMDR1=HmQDKu5iS3MaOmBSzLhVuwQxQJUOZAOWV6p3jDw@mail.gmail.com> (raw)
In-Reply-To: <CAH2-KxDuADgU1+hfyLXzvfu5C7Z-rZp73HYDfyCHee01dSirrA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 574 bytes --]
Thank you Brad!
On Sat, Jan 30, 2021 at 2:23 PM Ed Tanous <edtanous@google.com> wrote:
> On Sat, Jan 30, 2021 at 2:19 PM Brad Bishop <bradleyb@fuzziesquirrel.com>
> wrote:
> >
> > On Thu, Jan 14, 2021 at 03:17:57PM -0800, Brandon Kim wrote:
> > >Hi everyone,
> > >
> > >Wanted to ping this thread to see if there were more concerns on
> creating
> > >an openbmc/google-misc repository.
> >
> > I finally created this today. Apologies to the Google team for the long
> > delay.
> >
> > -brad
>
> Awesome; Thanks for getting that done (especially on a Saturday).
>
> -Ed
>
[-- Attachment #2: Type: text/html, Size: 1014 bytes --]
prev parent reply other threads:[~2021-02-01 2:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-07 1:49 Upstreaming downstream Google BMC repositories Brandon Kim
2021-01-07 8:01 ` 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 [this message]
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='CALGRKGMDR1=HmQDKu5iS3MaOmBSzLhVuwQxQJUOZAOWV6p3jDw@mail.gmail.com' \
--to=brandonkim@google.com \
--cc=benjaminfair@google.com \
--cc=bradleyb@fuzziesquirrel.com \
--cc=ed@tanous.net \
--cc=edtanous@google.com \
--cc=openbmc@lists.ozlabs.org \
--cc=pmenzel@molgen.mpg.de \
/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.