Subject: Re: 2.4.19 merging?
From: Austin Gonyou <austin@coremetrics.com>
To: Nathan Straz <nstraz@sgi.com>
Cc: linux-xfs@oss.sgi.com
In-Reply-To: <20020408185745.GV16203@sgi.com>
References: <20020408185745.GV16203@sgi.com>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Date: 08 Apr 2002 14:09:26 -0500
Message-Id: <1018292966.30714.37.camel@UberGeek>
Mime-Version: 1.0
Sender: owner-linux-xfs@oss.sgi.com
Precedence: bulk

Ahhh! Ok. I understand. I guess I was getting confused. Sorry for the
static.

On Mon, 2002-04-08 at 13:57, Nathan Straz wrote:
> On Mon, Apr 08, 2002 at 07:06:13PM +0100, Christoph Hellwig wrote:
> > It's back at 2.4.18.  But this brings up another issue I wondered
> about
> > for some time:  In the good old days every prerelease was merged,
> nowdays
> > it's just the full releases.  Is there a reason behing this as the
> actual
> > XFS releases are for specific versions anyway and the CVS basically is
> > a current top-of-tree branch?
> 
> It's because it can take a fair amount of work to get the latest
> pre-release patch to merge into XFS.  2.5 is now the main development
> tree.  That tree is keeping up with pre-patches as Steve has time to
> merge them.  The 2.4 xfs tree is only being merged with major releases
> so Eric can spend less time merging and more time hunting down XFS bugs.
> 
> 
> -- 
> Nate Straz                                              nstraz@sgi.com
> sgi, inc                                           http://www.sgi.com/
> Linux Test Project                                  http://ltp.sf.net/
-- 
Austin Gonyou
Systems Architect, CCNA
Coremetrics, Inc.
Phone: 512-698-7250
email: austin@coremetrics.com

"It is the part of a good shepherd to shear his flock, not to skin it."
Latin Proverb