From: Amit Shah <amit.shah@redhat.com>
To: "Dr. David Alan Gilbert (git)" <dgilbert@redhat.com>
Cc: qemu-devel@nongnu.org, quintela@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2 1/4] Start migrating migration code into a migration directory
Date: Wed, 10 Dec 2014 08:01:28 +0530 [thread overview]
Message-ID: <20141210023128.GB6189@grmbl.mre> (raw)
In-Reply-To: <1418127333-5160-2-git-send-email-dgilbert@redhat.com>
On (Tue) 09 Dec 2014 [12:15:30], Dr. David Alan Gilbert (git) wrote:
> From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
>
> The migration code now occupies a fair chunk of the top level .c
> files, it seems time to give it it's own directory.
>
> I've not touched:
> arch_init.c - that's mostly RAM migration but has a few random other
> bits
> savevm.c - because it's built target specific
>
> This is purely a code move; no code has changed.
> - it fails checkpatch because of old violations, it feels safer
> to keep this as purely a move and fix those at some mythical future
> date.
Yea, git-am complains too.
Amit
next prev parent reply other threads:[~2014-12-10 2:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-09 12:15 [Qemu-devel] [PATCH v2 0/4] More migration file cleanup Dr. David Alan Gilbert (git)
2014-12-09 12:15 ` [Qemu-devel] [PATCH v2 1/4] Start migrating migration code into a migration directory Dr. David Alan Gilbert (git)
2014-12-10 2:31 ` Amit Shah [this message]
2014-12-09 12:15 ` [Qemu-devel] [PATCH v2 2/4] Remove migration- pre/post fixes off files in migration/ dir Dr. David Alan Gilbert (git)
2014-12-09 12:15 ` [Qemu-devel] [PATCH v2 3/4] Split struct QEMUFile out Dr. David Alan Gilbert (git)
2014-12-09 12:15 ` [Qemu-devel] [PATCH v2 4/4] Split the QEMU buffered file code out Dr. David Alan Gilbert (git)
2014-12-10 2:32 ` [Qemu-devel] [PATCH v2 0/4] More migration file cleanup Amit Shah
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=20141210023128.GB6189@grmbl.mre \
--to=amit.shah@redhat.com \
--cc=dgilbert@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@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).