On (Wed) 26 Oct 2016 [08:42:27], Eric Blake wrote:
> On 10/26/2016 01:07 AM, Amit Shah wrote:
> > On (Tue) 18 Oct 2016 [20:10:13], zhanghailiang wrote:
> >> configure --enable-colo/--disable-colo to switch COLO
> >> support on/off.
> >> COLO feature is enabled by default.
> >>
> >> Signed-off-by: zhanghailiang <[email protected]>
> >> Signed-off-by: Li Zhijian <[email protected]>
> >> Signed-off-by: Gonglei <[email protected]>
> >> Reviewed-by: Dr. David Alan Gilbert <[email protected]>
> >
> > Reviewed-by: Amit Shah <[email protected]>
> >
> >> v19:
> >> - fix colo_supported() to return true
> >> v11:
> >> - Turn COLO on in default (Eric's suggestion)
> >
> > Can you recap why the suggestion was made to switch it on by default?
>
> If the feature doesn't depend on external libraries, then enabling
> compilation by default will avoid bitrot.
Yes, that's fair, thanks.
> But mentioning this rationale in the commit message never hurts :)
Yep!
Amit
