From: "Daniel P. Berrange" <berrange@redhat.com>
To: Pranith Kumar <bobby.prani@gmail.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>, John Snow <jsnow@redhat.com>,
"open list:All patches CC here" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] Move README to markdown
Date: Fri, 15 Jul 2016 10:00:18 +0100 [thread overview]
Message-ID: <20160715090018.GB2317@redhat.com> (raw)
In-Reply-To: <20160715043111.29007-1-bobby.prani@gmail.com>
On Fri, Jul 15, 2016 at 12:31:11AM -0400, Pranith Kumar wrote:
> Move 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.
Agreed, you're not harming readability while in plain text, so
no reason not todo this IMHO.
>
> Signed-off-by: Pranith Kumar <bobby.prani@gmail.com>
Reviewed-by: Daniel P. Berrange <berrange@redhat.com>
> ---
> README => README.md | 41 ++++++++++++++++++++---------------------
> 1 file changed, 20 insertions(+), 21 deletions(-)
> rename README => README.md (85%)
>
> diff --git a/README b/README.md
> similarity index 85%
> rename from README
> rename to README.md
I'm ambivalent on the issue, but there's the option of having a symlink
in git from README.md -> README if people really want a file called
README to still exist.
Regards,
Daniel
--
|: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org -o- http://virt-manager.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|
next prev parent reply other threads:[~2016-07-15 9:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-15 4:31 [Qemu-devel] [PATCH] Move README to markdown Pranith Kumar
2016-07-15 9:00 ` Daniel P. Berrange [this message]
2016-07-15 11:37 ` Stefan Hajnoczi
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=20160715090018.GB2317@redhat.com \
--to=berrange@redhat.com \
--cc=bobby.prani@gmail.com \
--cc=jsnow@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
/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).