qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Yu Ning <yu.ning@linux.intel.com>
To: Thomas Huth <thuth@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Thomas Huth <huth@tuxfamily.org>,
	qemu-devel <qemu-devel@nongnu.org>, Stefan Weil <sw@weilnetz.de>
Cc: John Snow <jsnow@redhat.com>, Vincent Palatin <vpalatin@chromium.org>
Subject: Re: [Qemu-devel] HAXM is now open source
Date: Fri, 17 Nov 2017 16:34:08 +0800	[thread overview]
Message-ID: <541c82ef-9798-377a-8c79-f3aa0387324c@linux.intel.com> (raw)
In-Reply-To: <3cc5c809-001e-bb14-52fd-7a66ed00b38c@redhat.com>



On 11/17/2017 16:30, Thomas Huth wrote:
> On 17.11.2017 09:17, Yu Ning wrote:
> [...]
>> Is there a preferred document format for the QEMU blog, e.g. Markdown?
> Yes, we're using markdown of Jekyll (https://jekyllrb.com/docs/posts/).
> Please clone the qemu-web repository (see
> https://git.qemu.org/?p=qemu-web.git), and have a look in the "_posts"
> directory to see how the files should look like.
>
>> I'll get the content ready by early next week, and then I'll need
>> someone to help me post it.
> Sure, Paolo and I should be able to help. The preferred way is to create
> a patch against the qemu-web repository and send that patch to
> qemu-devel, with CC: to Paolo and myself. We then can give feedback, do
> sanity checking (in case you don't want to install Jekyll on your HD),
> and push the patch to the website if everything is fine.

Got it, thanks!

  reply	other threads:[~2017-11-17  8:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-14  8:54 [Qemu-devel] HAXM is now open source Yu Ning
2017-11-14 11:09 ` Thomas Huth
2017-11-14 19:13   ` John Snow
2017-11-15  8:25     ` Yu Ning
2017-11-15 14:18       ` Paolo Bonzini
2017-11-17  8:17         ` Yu Ning
2017-11-17  8:30           ` Thomas Huth
2017-11-17  8:34             ` Yu Ning [this message]
2017-11-17  8:53 ` Kamil Rytarowski
2017-11-17 10:30   ` Yu Ning
2017-11-17 11:09     ` Kamil Rytarowski

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=541c82ef-9798-377a-8c79-f3aa0387324c@linux.intel.com \
    --to=yu.ning@linux.intel.com \
    --cc=huth@tuxfamily.org \
    --cc=jsnow@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=sw@weilnetz.de \
    --cc=thuth@redhat.com \
    --cc=vpalatin@chromium.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).