All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pranith Kumar <bobby.prani@gmail.com>
Cc: qemu-devel@nongnu.org, famz@redhat.com, peter.maydell@linaro.org,
	berrange@redhat.com, sw@weilnetz.de, eblake@redhat.com,
	stefanha@gmail.com, armbru@redhat.com
Subject: [Qemu-devel] [PATCH 0/3] Fix regression caused my moving README
Date: Wed, 20 Jul 2016 15:39:52 -0400	[thread overview]
Message-ID: <20160720193955.21782-1-bobby.prani@gmail.com> (raw)

When we renamed README we caused a bunch of regressions caused by
checkpatch.pl and the windows installer which check for the presence
of the README file. The ensuring discussion made it clear that having
a symlink is preferable. This patch series implements that.

This works as expected and can be seen here: https://github.com/pranith/qemu/tree/markdown

Pranith Kumar (3):
  Revert e4dfc5e8e("Move README to markdown")
  Create README.md as a symlink to README
  Update README to accomodate markdown format

 README    | 105 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 README.md | 107 +-------------------------------------------------------------
 2 files changed, 106 insertions(+), 106 deletions(-)
 create mode 100644 README
 mode change 100644 => 120000 README.md

-- 
2.9.2

             reply	other threads:[~2016-07-20 19:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-20 19:39 Pranith Kumar [this message]
2016-07-20 19:39 ` [Qemu-devel] [PATCH 1/3] Revert e4dfc5e8e("Move README to markdown") Pranith Kumar
2016-07-20 20:14   ` Stefan Weil
2016-07-20 19:39 ` [Qemu-devel] [PATCH 2/3] Create README.md as a symlink to README Pranith Kumar
2016-07-20 19:39 ` [Qemu-devel] [PATCH 3/3] Update README to accomodate markdown format Pranith Kumar
2016-07-20 20:10   ` Stefan Weil
2016-07-20 20:21     ` Pranith Kumar
2016-07-20 21:29   ` Eric Blake
2016-07-20 21:33     ` Pranith Kumar
2016-07-20 21:41       ` Eric Blake
2016-07-20 22:07       ` Peter Maydell
2016-07-20 22:15         ` 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=20160720193955.21782-1-bobby.prani@gmail.com \
    --to=bobby.prani@gmail.com \
    --cc=armbru@redhat.com \
    --cc=berrange@redhat.com \
    --cc=eblake@redhat.com \
    --cc=famz@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.com \
    --cc=sw@weilnetz.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.