[Servercert-wg] [DRAFT] SC26 - Pandoc-Friendly Markdown Formatting Changes

[Jos Purvis (jopurvis)]

Whewf. Rather than continue to wrestle with the changes in my fork, I decided on a simpler change. I created the sc26-pandoc-friendly branch on the CA/B Forum repo, and then staged my changes there. That means you can now see exactly what’s changing with this compare:

            https://github.com/cabforum/documents/compare/SC26-pandoc-friendly

 

I’m sure there will still be a few bugs in there, but at least it’s up to date and easier to piece through what’s going on. I’ll leave the other PR open for now, but I’ll be amending this ballot with the compare instead so it’s clearer what’s going to change.

 

Thanks to Dimitris for the suggestion!

 

 

-- 
Jos Purvis (jopurvis at cisco.com)
.:|:.:|:. cisco systems  | Cryptographic Services
PGP: 0xFD802FEE07D19105  | +1 919.991.9114 (desk)

 

 

From: Ryan Sleevi <sleevi at google.com>
Date: Friday, January 17, 2020 at 2:46 PM
To: "Jos Purvis (jopurvis)" <jopurvis at cisco.com>, CABF Server Cert WG <servercert-wg at cabforum.org>
Subject: Re: [Servercert-wg] [DRAFT] SC26 - Pandoc-Friendly Markdown Formatting Changes

 

 

 

On Thu, Jan 16, 2020 at 4:11 PM Jos Purvis (jopurvis) via Servercert-wg <servercert-wg at cabforum.org> wrote:

Changes: The changes involved in the ballot are small formatting changes but large in number. As a result, rather than listing the changes individually, members are requested to review the redline of the ballot to see the differences. The pull request containing the set of changes to be implemented can be seen here:

            https://github.com/cabforum/documents/pull/142

 

More specifically, the set of changes to the Baseline Requirements document being proposed in this ballot is shown in this comparison:

            https://github.com/cabforum/documents/pull/142/files/93b31c97ec095766152bc67f1723c4dc40cb197e..f452eaa012fb6bc29530f4d91893f4b39a4b8af6

 

Er, wrong link? You picked commit  & commit-1 from your branch, which is mostly merging stuff in from our previous ballots.

 

There's still some minor tweaks needed to the pull request (e.g. https://github.com/cabforum/documents/pull/142/files#r340326196 ) that will update the commit hashes, but those don't touch the BRs themselves :)

 

I think you meant https://github.com/cabforum/documents/compare/16a5a9bb78a193266f8d1465de1ee5a1acf5d184...f452eaa012fb6bc29530f4d91893f4b39a4b8af6 as the canonical diff URL (i.e. substituting in the current head commit of cabforum/documents and the current head-commit of castillar/documents )

 

For viewing just the BR.md changes,  https://github.com/cabforum/documents/compare/16a5a9bb78a193266f8d1465de1ee5a1acf5d184...f452eaa012fb6bc29530f4d91893f4b39a4b8af6#diff-7f6d14a20e7f3beb696b45e1bf8196f2   (which is to say, clicking on "Files" and then "docs/br.md")

 

That's the *canonical* way to view the diff (and can be downloaded as a patch and viewed in your favorite diff tool). For example, I threw https://gist.github.com/sleevi/9230befcb952535337cb0afbd6295178/revisions together to compare those revisions based on the patch, which is roughly the same view without having to do a few clicks.

 

For those following, this is only complex because Jos is also including all the infrastructure to automatically generate the PDF and Word versions every time we make a chance, so there's both infrastructure files and the BR changes to go with it. For situations like this, we kind of need to do both at the same time.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://cabforum.org/pipermail/servercert-wg/attachments/20200130/64a1be4e/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3699 bytes
Desc: not available
URL: <http://cabforum.org/pipermail/servercert-wg/attachments/20200130/64a1be4e/attachment-0001.p7s>