On 10/08/2014 11:02 PM, Eric Blake wrote: > On 09/23/2014 03:23 AM, Yang Hongyang wrote: >> introduce an api colo_supported() to indicate COLO support, returns >> true if colo supported (configured with --enable-colo). >> >> Signed-off-by: Yang Hongyang <yan...@cn.fujitsu.com> >> --- > >> +++ b/include/migration/migration-colo.h >> @@ -0,0 +1,18 @@ >> +/* >> + * COarse-grain LOck-stepping Virtual Machines for Non-stop Service (COLO) >> + * (a.k.a. Fault Tolerance or Continuous Replication) >> + * >> + * Copyright (C) 2014 FUJITSU LIMITED >> + * >> + * This work is licensed under the terms of the GNU GPL, version 2. See >> + * the COPYING file in the top-level directory. > > Is there any reason you are forbidding the use of this file in a GPLv3 > project? We prefer new files to be GPLv2+, not GPLv2-only (by the use > of the "or later" clause), unless there is strong reason why it is not > possible.
I don't know the reason, and I think it is OK to be GPLv2+ Thanks Wen Congyang > > >> +++ b/migration-colo.c >> @@ -0,0 +1,16 @@ >> +/* >> + * COarse-grain LOck-stepping Virtual Machines for Non-stop Service (COLO) >> + * (a.k.a. Fault Tolerance or Continuous Replication) >> + * >> + * Copyright (C) 2014 FUJITSU LIMITED >> + * >> + * This work is licensed under the terms of the GNU GPL, version 2. See >> + * the COPYING file in the top-level directory. > > Same comment for all new files. >
