public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Ard Biesheuvel" <ard.biesheuvel@arm.com>
To: devel@edk2.groups.io, sean.brogan@microsoft.com,
	Laszlo Ersek <lersek@redhat.com>
Cc: "Kinney, Michael D" <michael.d.kinney@intel.com>
Subject: Re: [edk2-devel] [PATCH v1 2/6] ArmVirtPkg: Add Platform CI and configuration for Core CI
Date: Sun, 19 Apr 2020 11:35:55 +0200	[thread overview]
Message-ID: <fdd03f9e-d3d5-32a8-d59a-90e7ac6b43d4@arm.com> (raw)
In-Reply-To: <MW2PR2101MB0924AD8CC7805F3EACECF1A9E1D70@MW2PR2101MB0924.namprd21.prod.outlook.com>

On 4/19/20 10:29 AM, Sean via groups.io wrote:
> Laszlo,
> 
> Regarding your comments about disliking the verbosity of the markdown table/html table for build status both in Core Ci and now these Platform CI readme files.
> 
> As a learning experience I updated the OvmfPkg readme to use reStructuredText instead of markdown.  Not sure if I like RST but it does allow the links to not be in html and supports directives so you can push all that text to end of the file.
> 
> Do you like this enough that I should rework all three readmes and we should discuss if RST should be used instead of MD for the edk2 project?
> 
> RST version: https://github.com/spbrogan/edk2/blob/PlatformAndCoreCIForOvmfArmVirtEmulatorPackages_v8/OvmfPkg/README.rst
> MD version: https://github.com/spbrogan/edk2/blob/PlatformAndCoreCIForOvmfArmVirtEmulatorPackages_v7/OvmfPkg/README-pytools.md
> 

I think the rendered RST looks really good, and is perfectly usable as 
plaintext too. AFAICT, we are not losing out on anything the v7 version 
provided, right? If not, I am in favor of going with RST in this case, 
which I suppose implies that I am in favor of permitting it in EDK2 for 
purposes such as this one.

That does not necessarily imply that all markdown should be replaced 
with RST. I'm perfectly happy letting them co-exist, and I don't have an 
opinion on whether one should be recommended over the other, or which 
that should have to be.

> This is really the last remaining issue for the PlatformCI patchset.
> 

Agreed. This is converging really nicely.

-- 
Ard.


  reply	other threads:[~2020-04-19  9:35 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-19  8:29 [edk2-devel] [PATCH v1 2/6] ArmVirtPkg: Add Platform CI and configuration for Core CI Sean
2020-04-19  9:35 ` Ard Biesheuvel [this message]
2020-04-20 10:30   ` Laszlo Ersek
2020-04-19 20:56 ` Rebecca Cran
2020-04-20 11:08   ` Laszlo Ersek
2020-04-24 20:22     ` [EXTERNAL] " Bret Barkelew
  -- strict thread matches above, loose matches on Subject: below --
2020-04-09  8:05 Ard Biesheuvel
2020-04-09 19:57 ` [edk2-devel] " Sean
2020-04-15  6:55   ` Sean
2020-04-15 16:57     ` Laszlo Ersek
2020-04-15 19:31       ` Sean
2020-04-16 15:12         ` Laszlo Ersek
2020-04-15 17:18   ` Laszlo Ersek
2020-04-15 17:26     ` Ard Biesheuvel
2020-04-15 20:38     ` Sean
2020-04-16 14:51       ` Laszlo Ersek

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=fdd03f9e-d3d5-32a8-d59a-90e7ac6b43d4@arm.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