Date: Wed, 15 Sep 2004 16:05:54 -0700
From: Andrew Morton <akpm@osdl.org>
To: Chris Friesen <cfriesen@nortelnetworks.com>
Cc: adilger@clusterfs.com, mbligh@aracnet.com, anton@samba.org,
       linux-kernel@vger.kernel.org, paulus@samba.org
Subject: Re: offtopic: how to break huge patch into smaller independent
 patches?
Message-Id: <20040915160554.6d8350ca.akpm@osdl.org>
In-Reply-To: <4147C6D6.30508@nortelnetworks.com>
References: <41474B15.8040302@nortelnetworks.com>
	<20040915002023.GD5615@krispykreme>
	<119340000.1095209242@flay>
	<414799D1.7050609@nortelnetworks.com>
	<20040915014711.GA30607@schnapps.adilger.int>
	<4147C6D6.30508@nortelnetworks.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 948
Lines: 23

Chris Friesen <cfriesen@nortelnetworks.com> wrote:
>
> Andreas Dilger wrote:
> 
> > Consider using a source-control tool next time ;-/.  
> 
> We used a source control tool.  Its just not very useful when people do a port 
> from one kernel version to the next and submit it as one giant patch against the 
> new kernel rather than new versions of the original individual patches.
> 
> I'm the one planning how to avoid this problem in our next development cycle.
> 

What others said.

Once you apply those patches to your baseline tree you're dead.  If your
primary revision-controlled objects are baseline+patch1+patch2+...+patchN
then life is much simpler when some smarty decides to uprev baseline.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/