qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Yoni Bettan <ybettan@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
	Eduardo Habkost <ehabkost@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 0/4] Reformatted INFO files to fit the Markdown (.md) format.
Date: Sun, 2 Sep 2018 20:59:33 +0300	[thread overview]
Message-ID: <2dc88142-38b0-4bc7-0dd1-f5b46533f84a@redhat.com> (raw)
In-Reply-To: <CAFEAcA9mSb-RQMkEr8p-BEUH65Y7Y4TDbMZJkJjWoo_z-iT9sg@mail.gmail.com>



On 9/2/18 8:13 PM, Peter Maydell wrote:
> On 2 September 2018 at 13:36, Yoni Bettan <ybettan@redhat.com> wrote:
>> This patch make INFO files (e.g. README, CODING_STYLE etc) much more
>> readable when watched from GitHub GUI.
>>
>> ./VERSION and ./MAINTAINERS were leave untouched otherwise
>> ./scripts/get_maintainer.pl breaks.
>>
>> ./COPYING and ./COPYING.LIB were leave untouched because it look likes
>> they come from GNU and not QEMU.
> Thanks for this patch, but we don't use Markdown format.
> We use RST for docs files, but README, CODING_STYLE, etc
> are just plain text and fine as they are I think.

Thanks for your reply.
I sent a V2 patch before I have noticed your response so if you could 
please copy your response to the V2 mail I will appreciate it.

Thanks,
Yoni
>
> -- PMM

  reply	other threads:[~2018-09-02 17:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-02 12:36 [Qemu-devel] [PATCH 0/4] Reformatted INFO files to fit the Markdown (.md) format Yoni Bettan
2018-09-02 12:36 ` [Qemu-devel] [PATCH 1/4] README.md : Reformatted " Yoni Bettan
2018-09-02 12:36 ` [Qemu-devel] [PATCH 2/4] CODING_STYLE.md " Yoni Bettan
2018-09-02 12:36 ` [Qemu-devel] [PATCH 3/4] HACKING.md " Yoni Bettan
2018-09-02 12:36 ` [Qemu-devel] [PATCH 4/4] LICENSE.md " Yoni Bettan
2018-09-02 17:13 ` [Qemu-devel] [PATCH 0/4] Reformatted INFO files " Peter Maydell
2018-09-02 17:59   ` Yoni Bettan [this message]
2018-09-02 18:00 ` Yoni Bettan

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=2dc88142-38b0-4bc7-0dd1-f5b46533f84a@redhat.com \
    --to=ybettan@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=peter.maydell@linaro.org \
    --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).