openbmc.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Jeff9 Chan(陳松儉_ASRockRack)" <Jeff9_Chan@asrockrack.com>
To: Bradley W Bishop <bradleyb@us.ibm.com>,
	"openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>
Cc: "manager@lfprojects.org" <manager@lfprojects.org>
Subject: RE: OPENBMC ASRock Rack
Date: Tue, 8 Jun 2021 02:01:01 +0000	[thread overview]
Message-ID: <cb87a8f3a17f47e192ab5474a331807c@asrockrack.com> (raw)
In-Reply-To: 7807e4794c844beda004d7059c74289c@asrockrack.com

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

Re-send

Hi Bradley,
        I got below error when I try to push meta-asrockrack layer to gerrit.
        Is that means my email is not listed in the list?

To ssh://openbmc.gerrit/openbmc/openbmc
! [remote rejected]     HEAD -> refs/for/master (commit 1d9951c: not Signed-off-by author/committer/uploader in message footer)
error: failed to push some refs to 'ssh://openbmc.gerrit/openbmc/openbmc'

        My procedure is:

1.      Git clone openbmc

2.      Add meta-asrockrack layer

3.      git remote add gerrit ssh://openbmc.gerrit/openbmc/openbmc

4.      git commit

5.      git push gerrit

My git log:
commit 1d9951c5518a7bdf88a5de16a41ae2f337e1b2ed (HEAD -> master)
Author: Jeff9Chan <jeff9_chan@asrockrack.com>
Date:   Tue Jun 8 09:15:44 2021 +0800

    add meta-asrockrack layer
    Signed-off-by: Jeff Chan <Jeff9_Chan@asrockrack.com>

    Change-Id: I1686133e0093e4e00adeadc068972396c8dc4fab


best regards

Jeff Chan
ASRock Inc.
Tel: +886-2-55599600 ext.38670

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

       reply	other threads:[~2021-06-08  2:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <dbe431da08674c61bcda091cec16b5fb@asrockrack.com>
     [not found] ` <5d74d92b8e2f47acab7da6a54f6c18ee@asrockrack.com>
     [not found]   ` <fec2cbe8fd144a52915d971b4e7214bb@asrockrack.com>
     [not found]     ` <58f7b059987f40b78ebdcdbd1db5d969@asrockrack.com>
     [not found]       ` <8a3b99b118744df5a918b43e5520d35a@asrockrack.com>
     [not found]         ` <CALVHhedqJhfKD+MNofiwnKBB7sGG1wRPV4gXTdW_h=8=6=4HKw@mail.gmail.com>
     [not found]           ` <OF6DE94A96.B5787DB8-ON00258584.00525E62-00258584.0052E3DC@notes.na.collabserv.com>
     [not found]             ` <OF796A58B2.9DA64EBD-ON00258585.003E519E-00258585.003F6F0E@notes.na.collabserv.com>
     [not found]               ` <OF2B5AA3C5.40A65716-ON00258589.004350E5-00258589.00436A50@notes.na.collabserv.com>
     [not found]                 ` <OF5B0F1DD8.7358EE61-ON002586BE.004FB2E2-002586BE.0050DCF8@notes.na.collabserv.com>
     [not found]                   ` <7807e4794c844beda004d7059c74289c@asrockrack.com>
2021-06-08  2:01                     ` Jeff9 Chan(陳松儉_ASRockRack) [this message]
2021-06-08  2:15                       ` OPENBMC ASRock Rack Ed Tanous
2021-06-08  5:59                       ` Joel Stanley
2021-06-08  6:47                         ` Jeff9 Chan(陳松儉_ASRockRack)
2021-07-08  1:49                         ` Jeff9 Chan(陳松儉_ASRockRack)
2021-07-08 20:54                           ` Ed Tanous
2021-06-08  2:44                     ` Milton Miller II
2021-06-08  3:50                       ` Jeff9 Chan(陳松儉_ASRockRack)
2021-06-08  5:44 Milton Miller II

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=cb87a8f3a17f47e192ab5474a331807c@asrockrack.com \
    --to=jeff9_chan@asrockrack.com \
    --cc=bradleyb@us.ibm.com \
    --cc=manager@lfprojects.org \
    --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 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).