From: "Daniel P. Berrange" <berrange@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org, Pranith Kumar <bobby.prani@gmail.com>
Subject: Re: [Qemu-devel] [PULL 09/12] Move README to markdown
Date: Tue, 19 Jul 2016 16:49:48 +0100 [thread overview]
Message-ID: <20160719154948.GJ21295@redhat.com> (raw)
In-Reply-To: <1468917259-8475-10-git-send-email-pbonzini@redhat.com>
On Tue, Jul 19, 2016 at 10:34:16AM +0200, Paolo Bonzini wrote:
> From: Pranith Kumar <bobby.prani@gmail.com>
>
> 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.
>
> Signed-off-by: Pranith Kumar <bobby.prani@gmail.com>
> Message-Id: <20160715043111.29007-1-bobby.prani@gmail.com>
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
> ---
> README => README.md | 41 ++++++++++++++++++++---------------------
> 1 file changed, 20 insertions(+), 21 deletions(-)
> rename README => README.md (85%)
This has broken checkpatch.pl I'm afraid
$ git show 724b36ac355895953662d3ba41901873d66c0679 | perl ./scripts/checkpatch.pl -
Must be run from the top-level dir. of a kernel tree
It seems "README" is one of the filenames checkpatch.pl requirs to
be present.
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-19 15:49 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-19 8:34 [Qemu-devel] [PULL v2 00/12] Misc patches for 2.7 hard freeze from 2016-07-18 Paolo Bonzini
2016-07-19 8:34 ` [Qemu-devel] [PULL 01/12] use g_path_get_dirname instead of dirname Paolo Bonzini
2016-07-19 8:34 ` [Qemu-devel] [PULL 02/12] Changed malloc to g_malloc, free to g_free in bsd-user/qemu.h Paolo Bonzini
2016-07-19 8:34 ` [Qemu-devel] [PULL 03/12] hw/i386: add device tree support Paolo Bonzini
2016-07-19 8:34 ` [Qemu-devel] [PULL 04/12] compiler: never omit assertions if using a static analysis tool Paolo Bonzini
2016-07-19 8:34 ` [Qemu-devel] [PULL 05/12] megasas: remove useless check for cmd->frame Paolo Bonzini
2016-07-19 8:34 ` [Qemu-devel] [PULL 06/12] checkpatch: consider git extended headers valid patches Paolo Bonzini
2016-07-19 8:34 ` [Qemu-devel] [PULL 07/12] exec: avoid realloc in phys_map_node_reserve Paolo Bonzini
2016-07-19 8:34 ` [Qemu-devel] [PULL 08/12] cpu-exec: Move down some declarations in cpu_exec() Paolo Bonzini
2016-07-19 8:34 ` [Qemu-devel] [PULL 09/12] Move README to markdown Paolo Bonzini
2016-07-19 15:49 ` Daniel P. Berrange [this message]
2016-07-19 18:15 ` Pranith Kumar
2016-07-19 20:54 ` Peter Maydell
2016-07-19 8:34 ` [Qemu-devel] [PULL 10/12] block/iscsi: fix rounding in iscsi_allocationmap_set Paolo Bonzini
2016-07-19 8:34 ` [Qemu-devel] [PULL 11/12] block/iscsi: allow caching of the allocation map Paolo Bonzini
2016-07-19 8:34 ` [Qemu-devel] [PULL 12/12] target-i386: Remove redundant HF_SOFTMMU_MASK Paolo Bonzini
2016-07-19 15:39 ` [Qemu-devel] [PULL v2 00/12] Misc patches for 2.7 hard freeze from 2016-07-18 Peter Maydell
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=20160719154948.GJ21295@redhat.com \
--to=berrange@redhat.com \
--cc=bobby.prani@gmail.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).