From: "Laszlo Ersek" <lersek@redhat.com>
To: Leif Lindholm <leif.lindholm@linaro.org>, "Ni, Ray" <ray.ni@intel.com>
Cc: "Gao, Liming" <liming.gao@intel.com>,
"Cetola, Stephano" <stephano.cetola@intel.com>,
"Kinney, Michael D" <michael.d.kinney@intel.com>,
"Jayanth.Raghuram@dell.com" <Jayanth.Raghuram@dell.com>,
"'Andrew Fish (afish@apple.com)'" <afish@apple.com>,
"Wei.G.Liu@dell.com" <Wei.G.Liu@dell.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>
Subject: Re: [edk2-devel] [PATCH] MdePkg/DxeHstiLib: Added checks to improve error handling.
Date: Thu, 29 Aug 2019 16:24:12 +0200 [thread overview]
Message-ID: <f213e204-5f7c-fa8b-b660-e8ba0819ae65@redhat.com> (raw)
In-Reply-To: <20190829094942.GN29255@bivouac.eciton.net>
On 08/29/19 11:49, Leif Lindholm wrote:
> On Wed, Aug 28, 2019 at 05:33:28PM +0000, Ni, Ray wrote:
>> With the existence of mail attachments capability in new groups.io
>> system, can we accept such kind of patch submission? Or any side
>> effect you see if allowing mail attachments?
>
> Traditionally, the reason for not wanting patches as attachments is
> that it complicates doing inline code review as part of the email.
>
> If the mail system (let's take a wild guess, Outlook/Exchange?)
> doesn't corrupt the text *too* badly, I don't have an issue with the
> patch being sent in the message body *and* being attached so it could
> actually be applied.
>
> Alternatively, one could put the patch in the message body and a link
> to the patch in a public repo where it can be obtained.
I agree (with either alterative), as follows:
- The patch must be pasted manually in the message body, or it must be
attached.
- The patch must be published in a personal git repo, and the email
posting needs to reference that repo / branch.
- This is only acceptable as an exception to the workflow, and not as
the norm. (As long as our official contribution workflow is mailing list
based.)
- Doesn't work for patch series, only for single patches.
- v2, v3 and so iterations must use separate topic branches in the
submitter's personal repository. Non-fast-forward pushes to already
posted -- hence publicly referenced -- branches are not acceptable.
Effectively, once v(n) is posted, the submitter should consider the
matching topic branch in their own repo read-only.
- The edk2 package maintainer that ends up pushing the patch is
responsible for ensuring that the patch taken with "git fetch" for
integration is identical to the patch that was manually pasted by the
submitter.
The idea is that mailing list based review work as always, plus that the
patch that goes in ultimately be the same patch that got reviewed on the
list.
Thanks
Laszlo
next prev parent reply other threads:[~2019-08-29 14:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-26 19:54 [PATCH] MdePkg/DxeHstiLib: Added checks to improve error handling Jayanth.Raghuram
2019-08-27 1:56 ` Liming Gao
2019-08-27 18:29 ` Jayanth.Raghuram
2019-08-28 7:59 ` Liming Gao
2019-08-28 17:33 ` [edk2-devel] " Ni, Ray
2019-08-29 1:19 ` Jayanth.Raghuram
2019-08-29 14:28 ` Liming Gao
2019-08-29 9:49 ` Leif Lindholm
2019-08-29 14:24 ` Laszlo Ersek [this message]
2019-08-29 17:02 ` Ni, Ray
2019-08-30 2:21 ` Nate DeSimone
2019-08-30 11:52 ` Laszlo Ersek
2019-08-30 11:49 ` 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=f213e204-5f7c-fa8b-b660-e8ba0819ae65@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