Amit Shah wrote:
> On (Wed) 15 Jul 2015 [09:56:22], Juan Quintela wrote:
>> Previous commit only stored a valid state for migration. It stored the
>> empty string for savevm. Now, we are also storing the current state for
>> savevm.
>
> Can you include some more information in the commit message
On (Wed) 15 Jul 2015 [10:19:04], Juan Quintela wrote:
> Amit Shah wrote:
> > On (Wed) 15 Jul 2015 [09:56:22], Juan Quintela wrote:
> >> Previous commit only stored a valid state for migration. It stored the
> >> empty string for savevm. Now, we are also storing the current state for
> >> savevm.
Am 15.07.2015 um 10:18 schrieb Dr. David Alan Gilbert:
> * Juan Quintela (quint...@redhat.com) wrote:
>> Previous commit only stored a valid state for migration. It stored the
>> empty string for savevm. Now, we are also storing the current state for
>> savevm.
>>
>> Signed-off-by: Juan Quintela
* Juan Quintela (quint...@redhat.com) wrote:
> Previous commit only stored a valid state for migration. It stored the
> empty string for savevm. Now, we are also storing the current state for
> savevm.
>
> Signed-off-by: Juan Quintela
Reviewed-by: Dr. David Alan Gilbert
Looks OK to me; Chris
On (Wed) 15 Jul 2015 [09:56:22], Juan Quintela wrote:
> Previous commit only stored a valid state for migration. It stored the
> empty string for savevm. Now, we are also storing the current state for
> savevm.
Can you include some more information in the commit message? Like the
commit hash in
Previous commit only stored a valid state for migration. It stored the
empty string for savevm. Now, we are also storing the current state for
savevm.
Signed-off-by: Juan Quintela
---
include/migration/migration.h | 1 +
migration/migration.c | 2 +-
migration/savevm.c| 6 +
