Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755411Ab1DDTki (ORCPT ); Mon, 4 Apr 2011 15:40:38 -0400 Received: from smtp1.linux-foundation.org ([140.211.169.13]:46487 "EHLO smtp1.linux-foundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755198Ab1DDTkh (ORCPT ); Mon, 4 Apr 2011 15:40:37 -0400 Date: Mon, 4 Apr 2011 12:42:22 -0700 From: Andrew Morton To: "Serge E. Hallyn" Cc: "Serge E. Hallyn" , containers@lists.linux-foundation.org, Nathan Lynch , linux-kernel@vger.kernel.org, Alexey Dobriyan Subject: Re: [PATCH 05/10] Core checkpoint/restart support code Message-Id: <20110404124222.fd5eb85b.akpm@linux-foundation.org> In-Reply-To: <20110404185119.GB4782@peq.hallyn.com> References: <1298936432-29607-1-git-send-email-ntl@pobox.com> <1298936432-29607-6-git-send-email-ntl@pobox.com> <20110403190324.GD15044@hallyn.com> <1301929228.31531.39.camel@tp-t61> <20110404151017.GA4857@hallyn.com> <1301931608.31531.49.camel@tp-t61> <20110404162753.GA3456@hallyn.com> <20110404104119.78189678.akpm@linux-foundation.org> <20110404185119.GB4782@peq.hallyn.com> X-Mailer: Sylpheed 3.0.2 (GTK+ 2.20.1; x86_64-redhat-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1793 Lines: 38 On Mon, 4 Apr 2011 13:51:20 -0500 "Serge E. Hallyn" wrote: > Quoting Andrew Morton (akpm@linux-foundation.org): > > On Mon, 4 Apr 2011 11:27:53 -0500 "Serge E. Hallyn" wrote: > > > > > Andrew (Cc:d), did you see this thread go by, and it did it look > > > in any way more palatable to you? Have you had any thoughts on > > > checkpoint/restart in the last few months? Or did that horse quietly > > > die over winter? > > > > argh, it was the victim of LIFO. > > > > All I can say at this stage is that I'll be interested next time it > > comes past, sorry. > > Thanks, that's good to know. > > As you know, we started with a minimal patchset, then grew it over time > to answer the "but how will you (xyz) without uglifying the kernel". > Would you recommend we go back to keeping a separate minimal patchset, > or that we develop on the current, pretty feature-full version? I'm not > convinced believe there will be bandwidth to keep two trees and do both > justice. The minimal patchset is too minimal for Oren's use and the maximal patchset seems to have run aground on general kernel sentiment. So I guess you either take the minimal patchset and make it less minimal or take the maximal patchset and make it less maximal, ending up with the same thing. How's that for hand-waving useless obviousnesses :) One obvious approach is to merge the minimal patchset then, over time, sneak more stuff into it so we end up with the maximal patchset which people didn't like. Don't do that :) -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/