Got it. Reviewed-by: Liming Gao <[email protected]>

>-----Original Message-----
>From: Zhu, Yonghong
>Sent: Tuesday, April 03, 2018 4:29 PM
>To: Gao, Liming <[email protected]>; [email protected]
>Cc: Kinney, Michael D <[email protected]>; Shaw, Kevin W
><[email protected]>; Zhu, Yonghong <[email protected]>
>Subject: RE: [Patch] edk2-VfrSpecification: update version to 1.92
>
>Add the 1.92 version info in Revision History.
>
>Best Regards,
>Zhu Yonghong
>
>-----Original Message-----
>From: Gao, Liming
>Sent: Tuesday, April 3, 2018 4:28 PM
>To: Zhu, Yonghong <[email protected]>; [email protected]
>Cc: Kinney, Michael D <[email protected]>; Shaw, Kevin W
><[email protected]>
>Subject: RE: [Patch] edk2-VfrSpecification: update version to 1.92
>
>What change is here?
>
>>-----Original Message-----
>>From: Zhu, Yonghong
>>Sent: Tuesday, April 03, 2018 3:18 PM
>>To: [email protected]
>>Cc: Gao, Liming <[email protected]>; Kinney, Michael D
>><[email protected]>; Shaw, Kevin W <[email protected]>
>>Subject: [Patch] edk2-VfrSpecification: update version to 1.92
>>
>>Cc: Liming Gao <[email protected]>
>>Cc: Michael Kinney <[email protected]>
>>Cc: Kevin W Shaw <[email protected]>
>>Contributed-under: TianoCore Contribution Agreement 1.1
>>Signed-off-by: Yonghong Zhu <[email protected]>
>>---
>> README.md | 7 ++++---
>> 1 file changed, 4 insertions(+), 3 deletions(-)
>>
>>diff --git a/README.md b/README.md
>>index 0a596eb..3c40cab 100644
>>--- a/README.md
>>+++ b/README.md
>>@@ -1,9 +1,9 @@
>> <!--- @file
>>   README.md for EDK II VFR Programming Language Specification
>>
>>-  Copyright (c) 2007-2017, Intel Corporation. All rights reserved.<BR>
>>+  Copyright (c) 2007-2018, Intel Corporation. All rights reserved.<BR>
>>
>>   Redistribution and use in source (original document form) and 'compiled'
>>   forms (converted to PDF, epub, HTML and other formats) with or without
>>   modification, are permitted provided that the following conditions are met:
>>
>>@@ -70,11 +70,11 @@ PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
>LOSS
>>OF USE, DATA, OR PROFITS;  OR BUSINESS INTERRUPTION) HOWEVER
>CAUSED AND
>>ON ANY THEORY OF LIABILITY,  WHETHER IN CONTRACT, STRICT LIABILITY, OR
>>TORT (INCLUDING NEGLIGENCE OR
>> OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
>DOCUMENTATION,
>>EVEN IF  ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
>>
>>-Copyright (c) 2007-2017, Intel Corporation. All rights reserved.
>>+Copyright (c) 2007-2018, Intel Corporation. All rights reserved.
>>
>>
>> ### Revision History
>>
>> | Revision | Revision History
>>| Date              |
>>@@ -89,6 +89,7 @@ Copyright (c) 2007-2017, Intel Corporation. All
>>rights reserved.
>> | 1.60     | Update syntax for goto, image, questionref and constant value
>>opcodes, correct CALLBACK flag to INTEREACTIVE, correct help string for old
>>syntax date/time example, and add examples for expression opcodes.   |
>>December 1, 2011  |
>> | 1.70     | Clarify restriction that enum type and struct data filed with 
>> more
>>than one dimensions array are not supported.
>>| May 18, 2012      |
>> | 1.80     | Add syntax for warningif opcode, update definition for
>name/value
>>varstore and subtitle opcode, update referenced UEFI spec version info.
>>| Jan 14, 2014      |
>> | 1.90     | Correct sample code for catenate/match/cond opcode. Add
>syntax
>>for match2 opcode. Add sample code to show the buffer type constant value
>>for orderedlist opcode and default opcode.                            | July 
>>2, 2015      |
>> | 1.91     | Convert to Gitbook
>>| April 2017        |
>>-|          | [#683](https://bugzilla.tianocore.org/show_bug.cgi?id=683) VFR
>Spec:
>>Add union data type and bit fields in VFR Data Struct Definition
>>|                   |
>>+| 1.92     | [#683](https://bugzilla.tianocore.org/show_bug.cgi?id=683) VFR
>>Spec: Add union data type and bit fields in VFR Data Struct Definition
>>| March 2018        |
>>+
>>--
>>2.6.1.windows.1

_______________________________________________
edk2-devel mailing list
[email protected]
https://lists.01.org/mailman/listinfo/edk2-devel

Reply via email to