qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: Thomas Huth <thuth@redhat.com>, qemu-devel@nongnu.org
Cc: Paolo Bonzini <pbonzini@redhat.com>, Jason Wang <jasowang@redhat.com>
Subject: Re: [Qemu-devel] [qemu-web PATCH v2] Add a blog post about the new -nic parameter
Date: Wed, 30 May 2018 13:15:17 -0500	[thread overview]
Message-ID: <3846e12b-d2b3-a802-af9f-8a5d69b9794c@redhat.com> (raw)
In-Reply-To: <3171722d-aad9-39ad-7b24-6f80decf2747@redhat.com>

On 05/30/2018 12:27 PM, Thomas Huth wrote:
> On 30.05.2018 17:57, Eric Blake wrote:
>> On 05/30/2018 10:25 AM, Thomas Huth wrote:
>>> QEMU v2.12 features a new, useful parameter called "-nic". Let's
>>> throw some light on this new parameter with a new blog post.
>>>
>>> Signed-off-by: Thomas Huth <thuth@redhat.com>
>>> ---
>>
>>>   screenshots/2018-05-30-qemu-cli-net.png    | Bin 0 -> 24020 bytes
>>>   screenshots/2018-05-30-qemu-cli-netdev.png | Bin 0 -> 13553 bytes
>>
>> While binaries are necessary for use from within the blog, do you also
>> have source files that can be opened under gimp or other software for
>> easily tweaking the images?
> 
> I've created them with LibreOffice for my presentation at FOSDEM 2018
> ... I don't think we really want to check in .odp file into the
> repository, do we? It's also just some text and boxes, you can easily
> re-create that within minutes if it's ever necessary.

True, but even posting the .odp to the list (even if not stored in 
qemu-web.git) or including a URL to your presentation in the commit 
message (hoping that the URL is long-lasting), might save a few minutes 
for someone down the road trying to use the image as a starting point 
for a slightly different graphic.  (Or maybe I'm just spoiled by the GPL 
guaranteeing access to preferred-editing forms, whether for executables 
or for graphics - even if the blog isn't really under GPL)

> 
> Anyway, thanks for all the other corrections! ... I'll fix it up
> tomorrow and push the article.
> 
>   Thomas
> 

-- 
Eric Blake, Principal Software Engineer
Red Hat, Inc.           +1-919-301-3266
Virtualization:  qemu.org | libvirt.org

  reply	other threads:[~2018-05-30 18:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-30 15:25 [Qemu-devel] [qemu-web PATCH v2] Add a blog post about the new -nic parameter Thomas Huth
2018-05-30 15:57 ` Eric Blake
2018-05-30 16:01   ` Paolo Bonzini
2018-05-30 17:27   ` Thomas Huth
2018-05-30 18:15     ` Eric Blake [this message]
2018-05-30 18:33       ` Thomas Huth
2018-05-30 15:59 ` Paolo Bonzini

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=3846e12b-d2b3-a802-af9f-8a5d69b9794c@redhat.com \
    --to=eblake@redhat.com \
    --cc=jasowang@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).