All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Armbruster <armbru@redhat.com>
To: Max Reitz <mreitz@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
	qemu-devel@nongnu.org, qemu-block@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2 1/2] qapi/block-core: Overlays are not snapshots
Date: Wed, 05 Jun 2019 07:43:35 +0200	[thread overview]
Message-ID: <877ea0ege0.fsf@dusky.pond.sub.org> (raw)
In-Reply-To: <20190603202236.1342-2-mreitz@redhat.com> (Max Reitz's message of "Mon, 3 Jun 2019 22:22:35 +0200")

Max Reitz <mreitz@redhat.com> writes:

> A snapshot is something that reflects the state of something at a
> certain point in time.  It does not change.
>
> The file our snapshot commands create (or the node they install) is not
> a snapshot, as it does change over time.  It is an overlay.  We cannot
> do anything about the parameter names,

We certainly could: add new parameter, default to the old one, error out
when both are given, deprecate the old one.  Way more trouble than it's
worth.

If the QAPI machinery made such renames as simple as

    'overlay-file': {'type': 'str', 'alias': 'snapshot-file'}

we could consider it.  Of course, whether enhancing the machinery that
way would be worthwhile depends on complexity and on use.  I think we
got bigger fish to fry.

>                                        but we can at least adjust the
> descriptions to reflect that fact.
>
> Signed-off-by: Max Reitz <mreitz@redhat.com>
> Reviewed-by: Eric Blake <eblake@redhat.com>

Since you already got competent review, I merely glanced at the patches,
and didn't check for completeness.  No objections.


  reply	other threads:[~2019-06-05  5:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-03 20:22 [Qemu-devel] [PATCH v2 0/2] blockdev: Overlays are not snapshots Max Reitz
2019-06-03 20:22 ` [Qemu-devel] [PATCH v2 1/2] qapi/block-core: " Max Reitz
2019-06-05  5:43   ` Markus Armbruster [this message]
2019-06-03 20:22 ` [Qemu-devel] [PATCH v2 2/2] blockdev: " Max Reitz
2019-06-03 22:09 ` [Qemu-devel] [Qemu-block] [PATCH v2 0/2] " John Snow
2019-06-04  8:40 ` Alberto Garcia
2019-06-13 19:41 ` [Qemu-devel] " Max Reitz

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=877ea0ege0.fsf@dusky.pond.sub.org \
    --to=armbru@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=qemu-block@nongnu.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 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.