From: Laszlo Ersek <lersek@redhat.com>
To: "Kinney, Michael D" <michael.d.kinney@intel.com>
Cc: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: [RFC v2] GitBook documentation process
Date: Thu, 23 Mar 2017 19:40:54 +0100 [thread overview]
Message-ID: <c2c2b1dd-78a3-e862-02b8-6352258a5188@redhat.com> (raw)
In-Reply-To: <E92EE9817A31E24EB0585FDF735412F57D159522@ORSMSX113.amr.corp.intel.com>
On 03/23/17 18:37, Kinney, Michael D wrote:
> Laszlo,
>
> Yes. Those are Bugzilla TODO items. They are simple updates
> to add a new field and change required fields for documentation
> issues.
Thank you, that looks great!
Laszlo
>
>> -----Original Message-----
>> From: Laszlo Ersek [mailto:lersek@redhat.com]
>> Sent: Thursday, March 23, 2017 4:09 AM
>> To: Kinney, Michael D <michael.d.kinney@intel.com>
>> Cc: edk2-devel@lists.01.org
>> Subject: Re: [edk2] [RFC v2] GitBook documentation process
>>
>> On 03/23/17 05:14, Kinney, Michael D wrote:
>>> Hello,
>>>
>>> I have updated the GitBook RFC based on feedback received.
>>>
>>> Changes for V2:
>>> ===============
>>> * Remove [docs] from email subject
>>> * Update Bugzilla for document issues to remove Package
>>> field and add Document field
>>> ===============
>>
>>> * Use [TianoCore Bugzilla](https://bugzilla.tianocore.org) to report document
>> issues.
>>> + Add DocumentName as a required setting when reporting a document issue
>>> + Remove PackageName as a required setting when reporting a document issue
>>
>> So these are TODO items for the Bugzilla schema / WebUI?
>>
>> Thanks!
>> Laszlo
>
next prev parent reply other threads:[~2017-03-23 18:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-23 4:14 [RFC v2] GitBook documentation process Kinney, Michael D
2017-03-23 11:09 ` Laszlo Ersek
2017-03-23 17:37 ` Kinney, Michael D
2017-03-23 18:40 ` Laszlo Ersek [this message]
2017-03-28 17:48 ` Kinney, Michael D
2017-03-31 23:07 ` Kinney, Michael D
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=c2c2b1dd-78a3-e862-02b8-6352258a5188@redhat.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