From: "Chang, Abner via groups.io" <abner.chang=amd.com@groups.io>
To: Mike Maslenkin <mike.maslenkin@gmail.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>
Cc: "nicklew@nvidia.com" <nicklew@nvidia.com>,
"igork@ami.com" <igork@ami.com>
Subject: Re: [edk2-devel] [edk2-redfish-client][PATCH v2 0/3] change method for provisioning + minor fixes
Date: Tue, 19 Dec 2023 02:04:27 +0000 [thread overview]
Message-ID: <MN2PR12MB3966B1427CEF6F86EBB64367EA97A@MN2PR12MB3966.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20231219010023.56603-1-mike.maslenkin@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1605 bytes --]
[AMD Official Use Only - General]
Hi Mike,
According the conversation I had with Rebecca, please update your copyright that follow below format on the later patches you send; as you use the individual contributor copyright.
Copyright (c) FIRST - LAST, Contributor <Contributor's email > <BR>
Thanks
Abner
> -----Original Message-----
> From: Mike Maslenkin <mike.maslenkin@gmail.com>
> Sent: Tuesday, December 19, 2023 9:00 AM
> To: devel@edk2.groups.io
> Cc: Chang, Abner <Abner.Chang@amd.com>; nicklew@nvidia.com;
> igork@ami.com; Mike Maslenkin <mike.maslenkin@gmail.com>
> Subject: [edk2-redfish-client][PATCH v2 0/3] change method for provisioning
> + minor fixes
>
> Caution: This message originated from an External Source. Use proper caution
> when opening attachments, clicking links, or responding.
>
>
> This patch set contains minor fixes.
>
> diff from v1:
> original patch 4/4 with change related to BIOS resources provisioning
> removed.
>
> PR: https://github.com/tianocore/edk2-redfish-client/pull/64
>
> Cc: Abner Chang <abner.chang@amd.com>
> Cc: Igor Kulchytskyy <igork@ami.com>
> Cc: Nickle Wang <nicklew@nvidia.com>
> Signed-off-by: Mike Maslenkin <mike.maslenkin@gmail.com>
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#112663): https://edk2.groups.io/g/devel/message/112663
Mute This Topic: https://groups.io/mt/103255134/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
[-- Attachment #2: Type: message/rfc822, Size: 3006 bytes --]
From: "Chang, Abner" <Abner.Chang@amd.com>
To: Rebecca Cran <rebecca@bsdio.com>, "devel@edk2.groups.io" <devel@edk2.groups.io>
Subject: RE: [edk2-devel] Copyright for an individual contributor
Date: Tue, 19 Dec 2023 01:38:42 +0000
Message-ID: <MN2PR12MB3966AF722E06DD8D64EBBCA2EA97A@MN2PR12MB3966.namprd12.prod.outlook.com>
Hmm, ok, thanks Rebecca.
So that would be:
Copyright (c) FIRST - LAST, Contributor <Contributor’s email > <BR>
Thanks
Abner
> -----Original Message-----
> From: Rebecca Cran <rebecca@bsdio.com>
> Sent: Monday, December 18, 2023 1:37 PM
> To: devel@edk2.groups.io; Chang, Abner <Abner.Chang@amd.com>
> Subject: Re: [edk2-devel] Copyright for an individual contributor
>
> Caution: This message originated from an External Source. Use proper caution
> when opening attachments, clicking links, or responding.
>
>
> On 12/17/23 20:01, Chang, Abner via groups.io wrote:
> >
> > [AMD Official Use Only - General]
> >
> >
> > Hi all,
> >
> > How do we have the copyright for the contribution from an individual?
> > I don’t see the formatting defined in edk2 C coding standard. Is the
> > below format ok?
> >
> > Copyright (c) 2023, Contributor <Contributor’s email >
> >
>
> I think to follow the style guide, it should have a "<BR>" at the end,
> though most files with copyrights from individuals don't have that.
>
>
> --
>
> Rebecca Cran
next prev parent reply other threads:[~2023-12-19 2:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-19 1:00 [edk2-devel] [edk2-redfish-client][PATCH v2 0/3] change method for provisioning + minor fixes Mike Maslenkin
2023-12-19 1:00 ` [edk2-devel] [edk2-redfish-client][PATCH v2 1/3] RedfishClientPkg: add check for NULL pointer to avoid ASSERT Mike Maslenkin
2023-12-19 3:40 ` Chang, Abner via groups.io
2023-12-19 1:00 ` [edk2-devel] [edk2-redfish-client][PATCH v2 2/3] RedfishClientPkg: fix typo in EfiRestJsonStructureProtocolIsReady Mike Maslenkin
2023-12-19 3:40 ` Chang, Abner via groups.io
2023-12-19 1:00 ` [edk2-devel] [edk2-redfish-client][PATCH v2 3/3] RedfishClientPkg: fix access to unitialized variable Mike Maslenkin
2023-12-19 3:40 ` Chang, Abner via groups.io
2023-12-19 2:04 ` Chang, Abner via groups.io [this message]
2023-12-19 2:39 ` [edk2-devel] [edk2-redfish-client][PATCH v2 0/3] change method for provisioning + minor fixes Mike Maslenkin
2023-12-19 3:38 ` Chang, Abner via groups.io
2024-01-03 8:33 ` Chang, Abner via groups.io
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=MN2PR12MB3966B1427CEF6F86EBB64367EA97A@MN2PR12MB3966.namprd12.prod.outlook.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