From: Kevin Wolf <kwolf@redhat.com>
To: Miguel Di Ciurcio Filho <miguel.filho@gmail.com>
Cc: armbru@redhat.com, qemu-devel@nongnu.org, lcapitulino@redhat.com
Subject: [Qemu-devel] Re: [PATCH 0/3] snapshots: various updates
Date: Mon, 30 Aug 2010 16:39:53 +0200 [thread overview]
Message-ID: <4C7BC2B9.4080005@redhat.com> (raw)
In-Reply-To: <1280944550-6502-1-git-send-email-miguel.filho@gmail.com>
Am 04.08.2010 19:55, schrieb Miguel Di Ciurcio Filho:
> Hi there!
>
> This series introduces updates the 'info snapshots' and 'savevm' commands.
>
> Patch 1 summarizes the output of 'info snapshots' to show only fully
> available snapshots.
>
> Patch 2 adds a default name to an snapshot in case the user did not provide one,
> using a template like vm-YYYYMMDDHHMMSS.
>
> Patch 3 adds -f to the 'savevm' command in case the use really wants to
> overwrite an snapshot.
>
> More details in each patch.
>
> Changelog from previous version:
> --------------------------------
> - libvirt is not affected by the change in savevm
> - Fixed some coding errors and do not rename the name of variables
Thanks, applied patch 1 and 2 to the block branch. Commented on patch 3.
Kevin
prev parent reply other threads:[~2010-08-30 14:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-04 17:55 [Qemu-devel] [PATCH 0/3] snapshots: various updates Miguel Di Ciurcio Filho
2010-08-04 17:55 ` [Qemu-devel] [PATCH 1/3] monitor: make 'info snapshots' show only fully available snapshots Miguel Di Ciurcio Filho
2010-08-04 17:55 ` [Qemu-devel] [PATCH 2/3] savevm: Generate a name when run without one Miguel Di Ciurcio Filho
2010-08-04 17:55 ` [Qemu-devel] [PATCH 3/3] savevm: prevent snapshot overwriting Miguel Di Ciurcio Filho
2010-08-30 14:28 ` [Qemu-devel] " Kevin Wolf
2010-08-30 14:39 ` Kevin Wolf [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=4C7BC2B9.4080005@redhat.com \
--to=kwolf@redhat.com \
--cc=armbru@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=miguel.filho@gmail.com \
--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 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).