From: "Rebecca Cran" <rebecca@bsdio.com>
To: "Gerd Hoffmann" <kraxel@redhat.com>,
"Marvin Häuser" <mhaeuser@posteo.de>
Cc: edk2-devel-groups-io <devel@edk2.groups.io>,
Michael Kinney <michael.d.kinney@intel.com>
Subject: Re: [edk2-devel] [edk2-platforms] Enable GitHub PR, protected branches, and 'push' label
Date: Fri, 17 Mar 2023 08:22:39 -0600 [thread overview]
Message-ID: <99e6941a-a05f-26de-4dfa-de6ff6d067e1@bsdio.com> (raw)
In-Reply-To: <20230317134433.nl5auf5u55jvfw4t@sirius.home.kraxel.org>
On 3/17/23 7:44 AM, Gerd Hoffmann wrote:
> Agree. Also from the web-based review tools I've worked with so far
> (not much, only github and gitlab) github is the better one.
Having used Review Board, Gitlab, Github, Phabricator, Gerrit and
probably others, Gerrit is by far my least favorite.
I haven't enjoyed the GitHub UI compared to Gitlab or Phabricator, but I
can live with it without too much frustration.
--
Rebecca Cran
next prev parent reply other threads:[~2023-03-17 14:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-17 12:32 [edk2-devel] [edk2-platforms] Enable GitHub PR, protected branches, and 'push' label Marvin Häuser
2023-03-17 12:57 ` Rebecca Cran
2023-03-17 13:44 ` Gerd Hoffmann
2023-03-17 14:08 ` Marvin Häuser
2023-03-17 14:20 ` Rebecca Cran
2023-03-17 15:37 ` Michael D Kinney
2023-03-17 14:22 ` Rebecca Cran [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-03-15 20:02 Michael D Kinney
2023-03-15 22:24 ` [edk2-devel] " Marvin Häuser
2023-03-15 22:34 ` Michael D Kinney
2023-03-16 19:54 ` Marvin Häuser
2023-03-16 19:59 ` Rebecca Cran
2023-03-17 9:33 ` Gerd Hoffmann
2023-03-17 10:36 ` Rebecca Cran
2023-03-17 10:48 ` Rebecca Cran
[not found] ` <174D2F2BAAB7643C.10271@groups.io>
2023-03-17 10:57 ` Rebecca Cran
2023-03-17 15:27 ` Michael D Kinney
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=99e6941a-a05f-26de-4dfa-de6ff6d067e1@bsdio.com \
--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