All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] QEMU related blogs, all in once place
Date: Fri, 26 Jan 2018 13:39:44 +0000	[thread overview]
Message-ID: <20180126133944.GE1556@redhat.com> (raw)
In-Reply-To: <CAJSP0QWfwAbQwDUH3-e87+fB+FLPjJT3tXjQcDpPrxf7Rk-0cw@mail.gmail.com>

On Fri, Jan 26, 2018 at 09:52:21AM +0000, Stefan Hajnoczi wrote:
> If you want to follow blogs from QEMU contributors check out:
> 
> https://planet.virt-tools.org/
> 
> Daniel Berrange has provided the following steps for adding your own
> blog to planet.virt-tools.org:
> 
>   $ git clone git://libvirt.org/virttools-planet.git
> 
> and add your blog info to updater/virt-tools/config.ini.
> 
> Optionally add a icon in updater/virt-tools/images/.
> 
> Then send the changes as a patch to libvir-list@redhat.com with
> git send-email.

Thanks for promoting this Stefan.

As the URL suggests, we are not merely looking for QEMU or libvirt developer's
blogs. We're interested in blogs from anyone who is involved in the open source
virtualization toools stack, xen, qemu, kvm, libvirt, spice, libguestfs,
virt-install, etc, etc, and likes writing blogs about it. Doesn't have to be
all raw tech details either, just as important are people writing user facing
blog content.

Regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|

      reply	other threads:[~2018-01-26 13:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-26  9:52 [Qemu-devel] QEMU related blogs, all in once place Stefan Hajnoczi
2018-01-26 13:39 ` Daniel P. Berrangé [this message]

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=20180126133944.GE1556@redhat.com \
    --to=berrange@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.