From: "Samer El-Haj-Mahmoud" <samer.el-haj-mahmoud@arm.com>
To: EDK II Development <devel@edk2.groups.io>,
"Kinney, Michael D" <michael.d.kinney@intel.com>
Cc: Samer El-Haj-Mahmoud <Samer.El-Haj-Mahmoud@arm.com>
Subject: EDK2 documents and wiki
Date: Wed, 11 Nov 2020 21:49:56 +0000 [thread overview]
Message-ID: <DB7PR08MB32609649B648C7B20BEDE7F090E80@DB7PR08MB3260.eurprd08.prod.outlook.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1320 bytes --]
I have a question on updating EDK2 documents and wiki.
I am trying to upload the SCT documents (contributed from UEFI Forum) to TianoCore Github and website. These are currently PDF and Word documents, so not suitable to be stand-alone markdown repos in https://github.com/tianocore-docs<https://github.com/tianocore-docsf> yet (like what is happening wiht the other specs). It seems that, at least for now, the best location as far as I can tell is:
1. Add the raw PDF /Word (ZIP) documents to https://github.com/tianocore-docs/Docs/tree/master/User_Docs
2. Update https://github.com/tianocore/tianocore.github.io/wiki/EDK-II-User-Documentation to point to the raw documents
For (1), should I send a patch to the list, or simply create a pull request with the files? I ask because I see a pull request pending since 2018 😊 (https://github.com/tianocore-docs/Docs/pull/1)
I assume for (2) I need to send a patch to the list, once (1) are uploaded.
Thanks,
--Samer
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
[-- Attachment #2: Type: text/html, Size: 9797 bytes --]
next reply other threads:[~2020-11-11 21:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-11 21:49 Samer El-Haj-Mahmoud [this message]
2020-11-12 4:20 ` EDK2 documents and wiki Michael D Kinney
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=DB7PR08MB32609649B648C7B20BEDE7F090E80@DB7PR08MB3260.eurprd08.prod.outlook.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