public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Feng, Bob C" <bob.c.feng@intel.com>
To: "Kinney, Michael D" <michael.d.kinney@intel.com>,
	"Gao, Liming" <liming.gao@intel.com>,
	"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: EDK II Specifications for edk2-stable201903 tag
Date: Thu, 7 Mar 2019 01:11:05 +0000	[thread overview]
Message-ID: <08650203BA1BD64D8AD9B6D5D74A85D1600A9FD6@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <E92EE9817A31E24EB0585FDF735412F5B8BB82FF@ORSMSX113.amr.corp.intel.com>

Hi Mike,

Yes. the Revision history need to update. I have sent the spec patches v2 which update the Revision History in README.md and table of content in SUMMARY.md for INF/FDF/DSC spec.
And I added the BZ in the README.md.

Thanks,
Bob

-----Original Message-----
From: Kinney, Michael D 
Sent: Thursday, March 7, 2019 12:59 AM
To: Gao, Liming <liming.gao@intel.com>; Feng, Bob C <bob.c.feng@intel.com>; edk2-devel@lists.01.org; Kinney, Michael D <michael.d.kinney@intel.com>
Subject: EDK II Specifications for edk2-stable201903 tag

Hi Liming and Bob,

I see several EDK II specification updates.

I do not see consistent updates to the Revision History In the README.md with link to the BZ for the document change.  Please make sure all revision histories are up to date with BZ links, and as each BZ is closed put the links to commits made in the BZ.  This allows anyone reading the documents to follow the link to the BZ from the Revision History, review the change request and follow the links to the commits in GitHub and the easily view the document changes.

Do you want released versions of these documents to align with the edk2-stable201903 tag?  The document release process is documented here:

https://github.com/tianocore-docs/edk2-TemplateSpecification/wiki/TianoCore-Documents-Releasing

If so, please enter BZ for each document with the requested release version number along with the SHA hash of on master the release branch is being requested.

Thanks,

Mike



      reply	other threads:[~2019-03-07  1:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-06 16:59 EDK II Specifications for edk2-stable201903 tag Kinney, Michael D
2019-03-07  1:11 ` Feng, Bob C [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=08650203BA1BD64D8AD9B6D5D74A85D1600A9FD6@SHSMSX101.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