From: "Yong Li" <yong.b.li@linux.intel.com>
To: "'Brad Bishop'" <bradleyb@fuzziesquirrel.com>
Cc: "'OpenBMC Maillist'" <openbmc@lists.ozlabs.org>,
"'Li, Yong B'" <yong.b.li@intel.com>
Subject: RE: Cannot find the submit button after "+2"
Date: Tue, 21 May 2019 09:05:14 +0800 [thread overview]
Message-ID: <000a01d50f71$3ff660d0$bfe32270$@linux.intel.com> (raw)
In-Reply-To: <20190520133130.ifmq4x2utuqqdzva@thinkpad.dyn.fuzziesquirrel.com>
Thanks Brad! Will contact the maintainers to merge my changes
Thanks,
Yong
-----Original Message-----
From: openbmc <openbmc-bounces+yong.b.li=linux.intel.com@lists.ozlabs.org>
On Behalf Of Brad Bishop
Sent: Monday, May 20, 2019 9:32 PM
To: Yong Li <yong.b.li@linux.intel.com>
Cc: 'OpenBMC Maillist' <openbmc@lists.ozlabs.org>; Li, Yong B
<yong.b.li@intel.com>
Subject: Re: Cannot find the submit button after "+2"
On Thu, May 16, 2019 at 09:46:50AM +0800, Yong Li wrote:
>Hi Brad,
>
>
>
>On the below code review I submitted, there are "+2" already, but I
>cannot find the submit button on the web page,
>
>
>
>Do I need to apply for other permissions or groups?
>
>
>
>https://gerrit.openbmc-project.xyz/#/c/openbmc/intel-ipmi-oem/+/17234/,
>
>
>
>Thanks,
>
>Yong
>
Hi Yong
Whether or not the patch author clicks submit or the maintainer clicks
submit is a matter of maintainer preference. I prefer to oversee the
merging of changes into the repositories I maintain. I know that other
maintainers perfer to approve the change but delegate the actual submission
to the patch author (and that is fine).
I'm working on assigning the owner permission to refs/* to the current
repository maintainer for each openbmc repository. This would allow each
repository maintainer to enable this (or not) as they see fit.
Thanks - brad
prev parent reply other threads:[~2019-05-21 1:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-16 1:46 Cannot find the submit button after "+2" Yong Li
2019-05-20 13:31 ` Brad Bishop
2019-05-21 1:05 ` Yong Li [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='000a01d50f71$3ff660d0$bfe32270$@linux.intel.com' \
--to=yong.b.li@linux.intel.com \
--cc=bradleyb@fuzziesquirrel.com \
--cc=openbmc@lists.ozlabs.org \
--cc=yong.b.li@intel.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.