From: Rebecca Cran <rebecca@bluestop.org>
To: Laszlo Ersek <lersek@redhat.com>, Evan Lloyd <Evan.Lloyd@arm.com>,
"ruiyu.ni@intel.com" <ruiyu.ni@intel.com>
Cc: "edk2-devel (edk2-devel@lists.01.org)" <edk2-devel@lists.01.org>
Subject: Re: Incorrect Author on patch
Date: Wed, 2 May 2018 12:31:57 -0600 [thread overview]
Message-ID: <12a7e14c-ca35-7a1a-8dcf-9aea25d2af2a@bluestop.org> (raw)
In-Reply-To: <948ba2ee-1f88-a346-14c8-815fb9b835c8@redhat.com>
On 5/2/2018 7:40 AM, Laszlo Ersek wrote:
> On 05/02/18 14:46, Evan Lloyd wrote:
>> I can well understand why it would be useful to use Gerrit as a means
>> of reviewing a patch - actually a brilliant idea,
> (actually, *not* a brilliant idea, but that's just my opinion :) )
*Please* not Gerrit. If we're going to use a code review system, please
let us choose Phabricator. It has a much nicer user interface.
You can see an example of the review requests it creates at
https://reviews.freebsd.org/differential/ .
--
Rebecca
next prev parent reply other threads:[~2018-05-02 18:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-25 15:02 Incorrect Author on patch Evan Lloyd
2018-04-25 21:14 ` Laszlo Ersek
2018-05-02 12:46 ` Evan Lloyd
2018-05-02 13:40 ` Laszlo Ersek
2018-05-02 18:31 ` Rebecca Cran [this message]
2018-05-02 15:20 ` Gao, Liming
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-list 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=12a7e14c-ca35-7a1a-8dcf-9aea25d2af2a@bluestop.org \
--to=devel@edk2.groups.io \
/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