qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Pranith Kumar <bobby.prani@gmail.com>
To: alex.bennee@linaro.org
Cc: qemu-devel@nongnu.org, stefanha@redhat.com,
	peter.maydell@linaro.org, berrange@redhat.com, eblake@redhat.com
Subject: [Qemu-devel] [PATCH 0/2] Add mardown formatting to README
Date: Thu, 16 Feb 2017 19:54:29 -0500	[thread overview]
Message-ID: <20170217005431.4016-1-bobby.prani@gmail.com> (raw)

Also create README.md as a symlink to README so that github displays
markdown.

Update the README file to markdown so that it makes the github page
look prettier. I know that github repo is a mirror and not the
official repo, but I think it doesn't hurt to have it in markdown
format.

The last time we tried, it caused issues for building installers and
the check patch. Creating a symlink will hopefully avoid those.

To compare, you can take a look at the following links:

old: https://github.com/pranith/qemu/
new: https://github.com/pranith/qemu/tree/readme

Pranith Kumar (2):
  Update README to accomodate markdown format
  Create README.md as a symlink to README

 README    | 44 +++++++++++++++++++++-----------------------
 README.md |  1 +
 2 files changed, 22 insertions(+), 23 deletions(-)
 create mode 120000 README.md

-- 
2.11.0

             reply	other threads:[~2017-02-17  0:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-17  0:54 Pranith Kumar [this message]
2017-02-17  0:54 ` [Qemu-devel] [PATCH 1/2] Update README to accomodate markdown format Pranith Kumar
2017-02-17  1:28   ` Nir Soffer
2017-02-17  0:54 ` [Qemu-devel] [PATCH 2/2] Create README.md as a symlink to README Pranith Kumar

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-all 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=20170217005431.4016-1-bobby.prani@gmail.com \
    --to=bobby.prani@gmail.com \
    --cc=alex.bennee@linaro.org \
    --cc=berrange@redhat.com \
    --cc=eblake@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    /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;
as well as URLs for NNTP newsgroup(s).