From: "Gao, Liming" <liming.gao@intel.com>
To: Felix Poludov <Felixp@ami.com>, "afish@apple.com" <afish@apple.com>
Cc: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: edk2 interface deprecation policy
Date: Fri, 1 Dec 2017 01:51:25 +0000 [thread overview]
Message-ID: <4A89E2EF3DFEDB4C8BFDE51014F606A14E188BBE@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <9333E191E0D52B4999CE63A99BA663A00302B64F9B@atlms1.us.megatrends.com>
Felix:
I agree to define the tag to specify the deprecated definition, library and drivers. If so, user can easily know which one is not used any more. But, I think we can still keep them in edk2 project, because they have no negative impact.
Thanks
Liming
>-----Original Message-----
>From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of
>Felix Poludov
>Sent: Friday, December 01, 2017 6:12 AM
>To: afish@apple.com
>Cc: edk2-devel@lists.01.org
>Subject: Re: [edk2] edk2 interface deprecation policy
>
>I agree. It would be beneficial to have a mailing list discussion on how to deal
>with the deprecated item.
>In some cases it would make sense to tag an interface as deprecated, but
>keep in the code base for a while (6 month?) before actually deleting it.
>
>-----Original Message-----
>From: afish@apple.com [mailto:afish@apple.com]
>Sent: Thursday, November 30, 2017 11:57 AM
>To: Felix Poludov
>Cc: edk2-devel@lists.01.org
>Subject: Re: [edk2] edk2 interface deprecation policy
>
>Felix,
>
>I don't think we have one....
>
>Adding new interfaces does not impact the downstream projects, but
>depreciating interface can break stuff. Seems like it might at least be a good
>idea to have a depreciation discussion on the mailing list. I'm open to other
>suggestions....
>
>Thanks,
>
>Andrew Fish
>
>> On Nov 30, 2017, at 6:00 AM, Felix Poludov <Felixp@ami.com> wrote:
>>
>> Does edk2 have a policy regarding deprecation of interface definition
>headers?
>> I can see that definition of the UgaDraw protocol that was deprecated years
>ago (I believe in UEFI 2.0) is still part of the code base; yet, definition of the
>SMM Communication ACPI Table that was deprecated this year in UEFI 2.6B
>has already been removed.
>>
>> Please consider the environment before printing this email.
>>
>> The information contained in this message may be confidential and
>proprietary to American Megatrends, Inc. This communication is intended to
>be read only by the individual or entity to whom it is addressed or by their
>designee. If the reader of this message is not the intended recipient, you are
>on notice that any distribution of this message, in any form, is strictly
>prohibited. Please promptly notify the sender by reply e-mail or by telephone
>at 770-246-8600, and then delete or destroy all copies of the transmission.
>> _______________________________________________
>> edk2-devel mailing list
>> edk2-devel@lists.01.org
>> https://lists.01.org/mailman/listinfo/edk2-devel
>
>
>Please consider the environment before printing this email.
>
>The information contained in this message may be confidential and
>proprietary to American Megatrends, Inc. This communication is intended to
>be read only by the individual or entity to whom it is addressed or by their
>designee. If the reader of this message is not the intended recipient, you are
>on notice that any distribution of this message, in any form, is strictly
>prohibited. Please promptly notify the sender by reply e-mail or by telephone
>at 770-246-8600, and then delete or destroy all copies of the transmission.
>_______________________________________________
>edk2-devel mailing list
>edk2-devel@lists.01.org
>https://lists.01.org/mailman/listinfo/edk2-devel
next prev parent reply other threads:[~2017-12-01 1:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-30 14:00 edk2 interface deprecation policy Felix Poludov
2017-11-30 16:56 ` Andrew Fish
2017-11-30 22:12 ` Felix Poludov
2017-12-01 1:51 ` Gao, Liming [this message]
2017-12-01 2:27 ` Ni, Ruiyu
2017-12-01 2:42 ` Zeng, Star
2017-12-01 12:01 ` Laszlo Ersek
2017-12-01 2:28 ` Zeng, Star
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=4A89E2EF3DFEDB4C8BFDE51014F606A14E188BBE@SHSMSX104.ccr.corp.intel.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