From: "Zhu, Yonghong" <yonghong.zhu@intel.com>
To: "Gao, Liming" <liming.gao@intel.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Cc: "Kinney, Michael D" <michael.d.kinney@intel.com>,
"Shaw, Kevin W" <kevin.w.shaw@intel.com>,
"Zhu, Yonghong" <yonghong.zhu@intel.com>
Subject: Re: [Patch] edk2-VfrSpecification: update version to 1.92
Date: Tue, 3 Apr 2018 08:29:15 +0000 [thread overview]
Message-ID: <B9726D6DCCFB8B4CA276A9169B02216D51FC2E85@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <4A89E2EF3DFEDB4C8BFDE51014F606A14E1F1918@SHSMSX104.ccr.corp.intel.com>
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 <yonghong.zhu@intel.com>; edk2-devel@lists.01.org
Cc: Kinney, Michael D <michael.d.kinney@intel.com>; Shaw, Kevin W <kevin.w.shaw@intel.com>
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: edk2-devel@lists.01.org
>Cc: Gao, Liming <liming.gao@intel.com>; Kinney, Michael D
><michael.d.kinney@intel.com>; Shaw, Kevin W <kevin.w.shaw@intel.com>
>Subject: [Patch] edk2-VfrSpecification: update version to 1.92
>
>Cc: Liming Gao <liming.gao@intel.com>
>Cc: Michael Kinney <michael.d.kinney@intel.com>
>Cc: Kevin W Shaw <kevin.w.shaw@intel.com>
>Contributed-under: TianoCore Contribution Agreement 1.1
>Signed-off-by: Yonghong Zhu <yonghong.zhu@intel.com>
>---
> 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
next prev parent reply other threads:[~2018-04-03 8:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-03 7:17 [Patch] Build Spec: Update Version to 1.28 Yonghong Zhu
2018-04-03 7:17 ` [Patch] DEC spec: Update version to 1.27 Yonghong Zhu
2018-04-03 8:34 ` Gao, Liming
2018-04-03 7:17 ` [Patch] DSC spec: Update version to 1.28 Yonghong Zhu
2018-04-03 8:34 ` Gao, Liming
2018-04-03 7:17 ` [Patch] edk2-VfrSpecification: update version to 1.92 Yonghong Zhu
2018-04-03 8:27 ` Gao, Liming
2018-04-03 8:29 ` Zhu, Yonghong [this message]
2018-04-03 8:34 ` Gao, Liming
2018-04-03 7:17 ` [Patch] Expression spec: update version to 1.3 Yonghong Zhu
2018-04-03 8:34 ` Gao, Liming
2018-04-03 7:17 ` [Patch] FDF spec: Update version to 1.28 Yonghong Zhu
2018-04-03 8:35 ` Gao, Liming
2018-04-03 7:17 ` [Patch] INF spec: Update version to 1.27 Yonghong Zhu
2018-04-03 8:35 ` Gao, Liming
2018-04-03 8:34 ` [Patch] Build Spec: Update Version to 1.28 Gao, Liming
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=B9726D6DCCFB8B4CA276A9169B02216D51FC2E85@SHSMSX103.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