From: Kashyap Chamarthy <kchamart@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Thomas Huth <thuth@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [qemu-web PATCH] New blog post: "QEMU in the blogs: February 2017"
Date: Tue, 21 Mar 2017 16:26:17 +0100 [thread overview]
Message-ID: <20170321152617.l7kvunlg4zgbmqsu@eukaryote> (raw)
In-Reply-To: <edbcad8a-f9e1-8fab-c47b-b1e899f74bfa@redhat.com>
On Tue, Mar 21, 2017 at 01:35:02PM +0100, Paolo Bonzini wrote:
>
>
> On 21/03/2017 13:30, Kashyap Chamarthy wrote:
> > On Tue, Mar 21, 2017 at 01:09:19PM +0100, Thomas Huth wrote:
> >> On 19.03.2017 10:46, Paolo Bonzini wrote:
> >>> Just an idea... If this is useful, we can do it every month. It only
> >>> takes ten minutes to skim planet.virt-tools.org and compile the list.
> >>
> >> Is it worth the effort? People can also quickly read through the planet
> >> blogs directly to get the same information...
> >
> > While that's true, I _guess_ Paolo did that for those audience who only
> > follow the QEMU blog feed, and forget that the planet.virt-tools.org
> > exists.
>
> Yeah, it's meant to be something easy to share or tweet (and it happens
> that ~1 per month is the frequency of my visits to planet.virt-tools.org).
>
> Also, it helps keeping the QEMU blog alive. :)
Yes, I agree, FWIW:
Reviewed-by: Kashyap Chamarthy <kchamart@redhat.com>
--
/kashyap
next prev parent reply other threads:[~2017-03-21 15:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-19 9:46 [Qemu-devel] [qemu-web PATCH] New blog post: "QEMU in the blogs: February 2017" Paolo Bonzini
2017-03-21 12:09 ` Thomas Huth
2017-03-21 12:30 ` Kashyap Chamarthy
2017-03-21 12:35 ` Paolo Bonzini
2017-03-21 15:26 ` Kashyap Chamarthy [this message]
2017-03-21 15:45 ` Laszlo Ersek
2017-03-21 15:50 ` Paolo Bonzini
2017-03-21 16:03 ` Laszlo Ersek
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=20170321152617.l7kvunlg4zgbmqsu@eukaryote \
--to=kchamart@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
/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).