From mboxrd@z Thu Jan 1 00:00:00 1970 From: Douglas Gilbert Subject: Re: [GIT PULL] final scsi updates for 2.6.34-rc1 Date: Sat, 13 Mar 2010 15:16:56 -0500 Message-ID: <4B9BF2B8.5090004@interlog.com> References: <1268242604.22601.25.camel@mulgrave.site> <1268418441.2802.61.camel@mulgrave.site> <2c0942db1003131135m1bea386dx4dd7990832cfbfea@mail.gmail.com> Reply-To: dgilbert@interlog.com Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from smtp.infotech.no ([82.134.31.41]:41059 "EHLO elrond.infotech.no" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1759075Ab0CMURF (ORCPT ); Sat, 13 Mar 2010 15:17:05 -0500 In-Reply-To: <2c0942db1003131135m1bea386dx4dd7990832cfbfea@mail.gmail.com> Sender: linux-scsi-owner@vger.kernel.org List-Id: linux-scsi@vger.kernel.org To: Ray Lee Cc: James Bottomley , Linus Torvalds , Andrew Morton , linux-scsi , linux-kernel Ray Lee wrote: > On Fri, Mar 12, 2010 at 10:27 AM, James Bottomley wrote: >> I do always have a tree ready in the first days of the merge window. It >> was, in fact, here: > > [...] > >> The slight problem is that I accumulate updates (like almost everyone >> else) from the few days before the merge window opened up until about >> the middle of the second week. That's what goes into the final pull, >> plus assorted bug fixes that showed up during the window. > > You appear to being using git as a sort of baroque CVS. Fixes that > arrive after the beginning of the merge window should be put into a > separate branch other than the one ready for submission. Features that > arrive after the beginning of the merge window should be placed into > yet another branch destined for the next merge window. Ray, I'm sure that James will appreciate your insightful advice. And Alan Cox is probably waiting for your thoughts on the design of serial device drivers. Amazing that after yet another Linus rant, people crawl out of the woodwork to attack the victim. Doug Gilbert