From: "Laszlo Ersek" <lersek@redhat.com>
To: Andrew Fish <afish@apple.com>,
Bret Barkelew <Bret.Barkelew@microsoft.com>
Cc: "devel@edk2.groups.io" <devel@edk2.groups.io>,
"spbrogan@outlook.com" <spbrogan@outlook.com>,
"rfc@edk2.groups.io" <rfc@edk2.groups.io>,
"Desimone, Nathaniel L" <nathaniel.l.desimone@intel.com>,
Mike Kinney <michael.d.kinney@intel.com>,
"Leif Lindholm (Nuvia address)" <leif@nuviainc.com>
Subject: Re: [EXTERNAL] [edk2-devel] [edk2-rfc] GitHub Pull Request based Code Review Process
Date: Mon, 25 May 2020 20:10:46 +0200 [thread overview]
Message-ID: <eb150a97-d89a-576f-24e7-98640f048802@redhat.com> (raw)
In-Reply-To: <2107AEA7-9145-4FC9-9E1A-C396F23877ED@apple.com>
Hi Andrew,
On 05/25/20 06:09, Andrew Fish wrote:
> I also found I had to Bing/Google to find the detailed instructions I
> needed as a developer, as the Wiki seems to assume you just know the
> Linux kernel patch process. That feels like an area we can improve.
(apologies if I've lost context; please disregard my message below in
that case).
I wrote the following wiki article originally in 2016:
https://github.com/tianocore/tianocore.github.io/wiki/Laszlo's-unkempt-git-guide-for-edk2-contributors-and-maintainers
I wrote it specifically for developers & maintainers with no (or almost
no) prior git / mailing list experience. Multiple developers confirmed
later that the article had helped them.
Thanks
Laszlo
next prev parent reply other threads:[~2020-05-25 18:10 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-19 7:21 [edk2-devel] [edk2-rfc] GitHub Pull Request based Code Review Process Nate DeSimone
2020-05-19 8:39 ` Laszlo Ersek
2020-05-19 18:02 ` Nate DeSimone
2020-05-19 16:54 ` Sean
2020-05-19 18:02 ` Nate DeSimone
2020-05-19 19:34 ` Bret Barkelew
2020-05-19 19:59 ` Nate DeSimone
2020-05-19 20:10 ` Bret Barkelew
2020-05-19 21:02 ` Nate DeSimone
2020-05-19 21:07 ` Bret Barkelew
2020-05-20 17:05 ` Laszlo Ersek
2020-05-20 17:21 ` Sean
2020-05-22 1:56 ` Andrew Fish
2020-05-20 21:53 ` Laszlo Ersek
2020-05-22 5:31 ` [EXTERNAL] " Bret Barkelew
2020-05-19 21:22 ` Laszlo Ersek
2020-05-19 21:35 ` Nate DeSimone
2020-05-19 21:38 ` Bret Barkelew
2020-05-19 20:41 ` Laszlo Ersek
2020-05-19 22:25 ` Sean
2020-05-21 13:30 ` Laszlo Ersek
2020-05-21 17:53 ` Sean
2020-05-22 2:59 ` Andrew Fish
2020-05-22 5:48 ` [EXTERNAL] " Bret Barkelew
2020-05-22 17:20 ` Laszlo Ersek
2020-05-25 4:09 ` [EXTERNAL] " Andrew Fish
2020-05-25 18:10 ` Laszlo Ersek [this message]
2020-05-25 18:28 ` Andrew Fish
2020-05-26 11:17 ` Laszlo Ersek
2020-05-26 14:39 ` Samer El-Haj-Mahmoud
2020-05-26 16:13 ` Bret Barkelew
2020-05-27 1:52 ` Bret Barkelew
2020-05-27 9:27 ` Tomas Pilar (tpilar)
2020-05-27 12:12 ` Laszlo Ersek
2020-05-27 22:07 ` Rebecca Cran
2020-05-27 17:39 ` Andrew Fish
2020-05-27 17:45 ` Bret Barkelew
2020-05-28 6:57 ` Bret Barkelew
2020-05-27 18:32 ` Laszlo Ersek
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=eb150a97-d89a-576f-24e7-98640f048802@redhat.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