From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCH 0/3 - resend] kvmclock reboot Date: Tue, 18 Mar 2008 13:00:15 +0200 Message-ID: <47DFA0BF.4020405@qumranet.com> References: <1205836206192-git-send-email-gcosta@redhat.com> <47DF9ED3.2070302@qumranet.com> <47DF9FAB.6030604@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: kvm-devel@lists.sourceforge.net, akpm@linux-foundation.org, virtualization@lists.linux-foundation.org To: Glauber Costa Return-path: In-Reply-To: <47DF9FAB.6030604@redhat.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: kvm-devel-bounces@lists.sourceforge.net Errors-To: kvm-devel-bounces@lists.sourceforge.net List-Id: kvm.vger.kernel.org Glauber Costa wrote: >> >> [Once a patchset has been applied and pushed (as seen on >> kvm-commits), I prefer incremental patches] >> > But I think this is a very good case of an exception, since the > applied patches would break bisect. I prefer to hear "damn glommer!" > because of that than "damn glommer!!" because of a broken bisect. I fold them up before sending to Linus anyway, so upstream bisect continues to work. For kvm.git, it's a choice between rewinding it a bit (which may confuse anyone who pulls) and breaking bisect. -- Do not meddle in the internals of kernels, for they are subtle and quick to panic. ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/