From: "Laszlo Ersek" <lersek@redhat.com>
To: devel@edk2.groups.io, philmd@redhat.com,
Rebecca Cran <rebecca@bluestop.org>,
liming.gao@intel.com, "Kinney,
Michael D" <michael.d.kinney@intel.com>,
"Cetola, Stephano" <stephano.cetola@intel.com>
Cc: Stephano Cetola <stephano.cetola@linux.intel.com>
Subject: Re: [edk2-devel] [PATCH] IntelFrameworkModulePkg: Fix comments and improve E820 debug output
Date: Fri, 12 Apr 2019 10:12:02 +0200 [thread overview]
Message-ID: <0cebbcb9-6c63-6896-396f-306ebc77fa6d@redhat.com> (raw)
In-Reply-To: <c7713260-d399-88fe-3252-a865930c2d10@redhat.com>
On 04/11/19 21:59, Philippe Mathieu-Daudé wrote:
> On 4/11/19 9:53 PM, Rebecca Cran wrote:
>> On 2019-04-11 13:30, Rebecca Cran via Groups.Io wrote:
>>>
>>> I'm sending emails on Thunderbird via Postfix, so there's no Outlook
>>> involved.
>>>
>>
>> Let's try again: I've unset the groups.io fields, so I wonder if that'll
>> change things.
>
> Yes, I see your From address correctly now.
Actually, I have to withdraw my previous confirmation.
When I wrote
"Me too. I stand corrected"
previously, I was replying to the copy of the thread that was delivered
to me directly. However, now that I'm looking at my list folder (i.e. at
messages reflected by groups.io), the only change that I'm seeing
between Rebecca's last two emails is:
- before: "Rebecca Cran via Groups.Io <rebecca=bluestop.org@groups.io>"
- after: "rebecca via Groups.Io <rebecca=bluestop.org@groups.io>"
So, if a maintainer applies a patch directly from the list, with git-am,
it will *still* not have right authorship information.
Thanks
Laszlo
>
> Now, how do we proceed to avoid the same problem with other users?
>
> IMHO a git pre-push hook on the maintainer side would be easier to maintain.
>
> Regards,
>
> Phil.
>
>
>
prev parent reply other threads:[~2019-04-12 8:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-04 17:56 [PATCH] IntelFrameworkModulePkg: Fix comments and improve E820 debug output Rebecca Cran
2019-04-05 9:05 ` [edk2-devel] " Philippe Mathieu-Daudé
2019-04-08 13:15 ` Liming Gao
[not found] ` <1593821D7C44BA9C.31892@groups.io>
2019-04-11 0:32 ` Liming Gao
2019-04-11 10:59 ` Philippe Mathieu-Daudé
2019-04-11 13:52 ` Liming Gao
2019-04-11 14:32 ` Philippe Mathieu-Daudé
2019-04-11 17:35 ` Laszlo Ersek
2019-04-11 19:30 ` Rebecca Cran
[not found] ` <1594824AB9352AE7.21554@groups.io>
2019-04-11 19:53 ` rebecca
2019-04-11 19:59 ` Philippe Mathieu-Daudé
2019-04-12 7:50 ` Laszlo Ersek
2019-04-12 8:12 ` Laszlo Ersek [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=0cebbcb9-6c63-6896-396f-306ebc77fa6d@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