[Rev 01] RFR: Introducing markdown

[Jesper Wilhelmsson]

Re-using the same branch to do additional changes to something already pushed seems to be a bad idea. The PR makes it look like all the commits in the branch are new. This is a link to the only new change (the rest is already reviewed and pushed to master):

https://github.com/openjdk/guide/pull/4/commits/d116159bead56fb725d5e884044dfadd76fc66b5

/Jesper

> On 14 May 2020, at 16:49, Jesper Wilhelmsson <jwilhelm at openjdk.java.net> wrote:
> 
>> Fixed a few bugs from html to markdown conversion.
> 
> Jesper Wilhelmsson has updated the pull request with a new target base due to a merge or a rebase. The incremental
> webrev excludes the unrelated changes brought in by the merge/rebase. The pull request contains six additional commits
> since the last revision:
> 
> - Merge remote-tracking branch 'upstream/master' into introducing_markdown
> - Fixed page title and minor bugs from html to markdown conversion.
> - Converted all html files to markdown
> - Moved files to src directory
> - Changed mode on image.
> - Populating the repo with the old html guide files.
> 
> -------------
> 
> Changes:
>  - all: https://git.openjdk.java.net/guide/pull/4/files
>  - new: https://git.openjdk.java.net/guide/pull/4/files/d116159b..72ca8428
> 
> Webrevs:
> - full: https://webrevs.openjdk.java.net/guide/4/webrev.01
> - incr: https://webrevs.openjdk.java.net/guide/4/webrev.00-01
> 
>  Stats: 0 lines in 0 files changed: 0 ins; 0 del; 0 mod
>  Patch: https://git.openjdk.java.net/guide/pull/4.diff
>  Fetch: git fetch https://git.openjdk.java.net/guide pull/4/head:pull/4
> 
> PR: https://git.openjdk.java.net/guide/pull/4