Re: [kvm-devel] [PATCH 0/3 - resend] kvmclock reboot
Avi Kivity wrote: > 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. > > ok, this wfm. I'll send incrementally next time. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
Re: [kvm-devel] [PATCH 0/3 - resend] kvmclock reboot
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/vse012070mrt/direct/01/ ___ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
Re: [kvm-devel] [PATCH 0/3 - resend] kvmclock reboot
Avi Kivity wrote: > Glauber Costa wrote: >> Avi, >> >> Hope this series is okay now. >> >> Thanks for the testing >> >> >> > > Applied, thanks. > > [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. - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
Re: [kvm-devel] [PATCH 0/3 - resend] kvmclock reboot
Glauber Costa wrote: > Avi, > > Hope this series is okay now. > > Thanks for the testing > > > Applied, thanks. [Once a patchset has been applied and pushed (as seen on kvm-commits), I prefer incremental patches] -- 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/vse012070mrt/direct/01/ ___ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
[kvm-devel] [PATCH 0/3 - resend] kvmclock reboot
Avi, Hope this series is okay now. Thanks for the testing - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel
