From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S263633AbTDYSTI (ORCPT ); Fri, 25 Apr 2003 14:19:08 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S263617AbTDYSTH (ORCPT ); Fri, 25 Apr 2003 14:19:07 -0400 Received: from bristol.phunnypharm.org ([65.207.35.130]:18829 "EHLO bristol.phunnypharm.org") by vger.kernel.org with ESMTP id S263635AbTDYSTG (ORCPT ); Fri, 25 Apr 2003 14:19:06 -0400 Date: Fri, 25 Apr 2003 14:16:10 -0400 From: Ben Collins To: Bill Davidsen Cc: Linux Kernel Mailing List Subject: Re: IEEE-1394 problem on init [ was Re: Linux 2.4.21-rc1 ] Message-ID: <20030425181610.GA2774@phunnypharm.org> References: <20030424214107.GH808@phunnypharm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.4i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org > Yes, and I miss why that matters. Let me see if I can make the idea clear > to you: > 2.4.22-pre5 some code > 2.4.22-pre5-bk1 fixes > 2.4.22-pre5-bk2 more fixes > 2.4.22-pre5-bk3 still more fixes > 2.4.22-pre6 fixes to date plus major changes > > So when a maintainer got something major it wouldn't go into bk (the > commercial software database) until a new -pre, while the -bk patches > available for download would get the fixes only. What if a fix depends on a major-change-patch? What if a fix is itself a major change? -- Debian - http://www.debian.org/ Linux 1394 - http://www.linux1394.org/ Subversion - http://subversion.tigris.org/ Deqo - http://www.deqo.com/