From: "Antoine Coeur" <Coeur@gmx.fr>
To: edk2-devel@lists.01.org
Subject: Re: [PATCH v2] ArmVirtPkg: Fix various typos
Date: Thu, 7 Feb 2019 18:13:58 +0100 [thread overview]
Message-ID: <trinity-566a8a51-1b40-493a-a3bb-813f1769e668-1549559638735@3c-app-gmx-bs64> (raw)
In-Reply-To: <1335c2cc-7697-96cb-9121-e8b88cbf31fe@redhat.com>
Thank you Laszlo.
Do you have any recommendations regarding the maximum size of a patch for smooth reviewing on this mailing list?
I have about 9000 lines of additional typos corrections in queue at https://github.com/Coeur/edk2/tree/typo, but I'm afraid that big patches will simply be ignored.
If I split them in small patches, how many patches can I post every day? Or should I post a hundred patches at the same time and reviewers won't freak out?
Or could we exceptionally allow pull requests on GitHub for those typos changes, as it doesn't involve actual code-change? That could be an interesting experiment that would prevent cluttering the mailing-list.
Coeur
Gesendet: Donnerstag, 07. Februar 2019 um 21:33 Uhr
Von: "Laszlo Ersek" <lersek@redhat.com>
An: "Antoine Coeur" <Coeur@gmx.fr>, edk2-devel@lists.01.org
Betreff: Re: [edk2] [PATCH v2] ArmVirtPkg: Fix various typos
Pushed as commit 7a90895306ac.
Thanks,
Laszlo
next prev parent reply other threads:[~2019-02-07 17:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-06 15:48 [PATCH v2] ArmVirtPkg: Fix various typos Antoine Coeur
2019-02-06 16:33 ` Laszlo Ersek
2019-02-06 22:33 ` Philippe Mathieu-Daudé
2019-02-07 13:33 ` Laszlo Ersek
2019-02-07 17:13 ` Antoine Coeur [this message]
2019-02-07 17:48 ` Philippe Mathieu-Daudé
2019-02-08 8:16 ` 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=trinity-566a8a51-1b40-493a-a3bb-813f1769e668-1549559638735@3c-app-gmx-bs64 \
--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