openbmc.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Brad Bishop <bradleyb@fuzziesquirrel.com>
To: 郁雷 <yulei.sh@bytedance.com>
Cc: openbmc <openbmc@lists.ozlabs.org>, xuxiaohan@bytedance.com
Subject: Re: Request to create new repo meta-bytedance
Date: Mon, 17 Aug 2020 16:01:33 -0400	[thread overview]
Message-ID: <8bd419da20bdfad6fc003145b15db3fb6c24e37d.camel@fuzziesquirrel.com> (raw)
In-Reply-To: <CAGm54UHBnv6YkFqCGmJE3Jkx_5gTY0ryaUov+kJGMvsb71kacg@mail.gmail.com>

On Wed, 2020-08-12 at 14:06 +0800, 郁雷 wrote:

> A kindly reminder, please help to add meta-bytedance into openbmc as
> subtree, thanks!

I finally did this today:

https://gerrit.openbmc-project.xyz/q/project:openbmc/openbmc+file:meta-bytedance

-brad

      reply	other threads:[~2020-08-17 20:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-15  6:28 Request to create new repo meta-bytedance 郁雷
2020-07-16 18:51 ` Brad Bishop
2020-08-12  6:06   ` [Phishing Risk] [External] " 郁雷
2020-08-17 20:01     ` Brad Bishop [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=8bd419da20bdfad6fc003145b15db3fb6c24e37d.camel@fuzziesquirrel.com \
    --to=bradleyb@fuzziesquirrel.com \
    --cc=openbmc@lists.ozlabs.org \
    --cc=xuxiaohan@bytedance.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).