From: "Rebecca Cran" <rebecca@bsdio.com>
To: Laszlo Ersek <lersek@redhat.com>, devel@edk2.groups.io
Cc: "Jordan Justen" <jordan.l.justen@intel.com>,
"Ard Biesheuvel" <ard.biesheuvel@arm.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>
Subject: Re: [edk2-devel] [PATCH v2] OvmfPkg: Add QemuFwCfgLibNull
Date: Thu, 30 Apr 2020 14:45:59 -0600 [thread overview]
Message-ID: <5af76add-11c9-5525-afa3-d81a1265482e@bsdio.com> (raw)
In-Reply-To: <279fcfc7-228f-ec56-14db-91c53c466694@redhat.com>
On 4/30/20 10:46 AM, Laszlo Ersek wrote:
>
> Please pay more attention to review feedback. If you post a new version
> without even attempting to address review comments, that's a waste of
> time for both you and your reviewers.
It's something I really do need to work on. I need to take a step back
and read up on effective ways of working with an email-based review
system, because at the moment I'm a bit overwhelmed with sorting through
the feedback, applying it (or not) etc. It's a new way of working, both
over email and with multi-patch series.
> (d) Please get your git setup in functional order *consistently*. This
> patch only adds new files (doesn't modify existing files), so there is
> no conflict due to <CR><CR><LF> on context lines or removed lines. But
> both new files have <CR><CR><LF> after the patch is applied with git-am.
I thought the SetupGit.py script should have done that, but reading
https://github.com/tianocore/tianocore.github.io/wiki/Laszlo's-unkempt-git-guide-for-edk2-contributors-and-maintainers
I see there's more I should configure.
--
Rebecca Cran
prev parent reply other threads:[~2020-04-30 20:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-30 13:22 [PATCH v2] OvmfPkg: Add QemuFwCfgLibNull Rebecca Cran
2020-04-30 16:46 ` [edk2-devel] " Laszlo Ersek
2020-04-30 20:45 ` Rebecca Cran [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-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=5af76add-11c9-5525-afa3-d81a1265482e@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