Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S266137AbUIOA34 (ORCPT ); Tue, 14 Sep 2004 20:29:56 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S269455AbUIOA3B (ORCPT ); Tue, 14 Sep 2004 20:29:01 -0400 Received: from ozlabs.org ([203.10.76.45]:35536 "EHLO ozlabs.org") by vger.kernel.org with ESMTP id S266128AbUIOAY4 (ORCPT ); Tue, 14 Sep 2004 20:24:56 -0400 Date: Wed, 15 Sep 2004 10:20:23 +1000 From: Anton Blanchard To: Chris Friesen Cc: Linux kernel , paulus@samba.org Subject: Re: offtopic: how to break huge patch into smaller independent patches? Message-ID: <20040915002023.GD5615@krispykreme> References: <41474B15.8040302@nortelnetworks.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <41474B15.8040302@nortelnetworks.com> User-Agent: Mutt/1.5.6+20040818i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 756 Lines: 20 > Its kind of offtopic, but I hoped that someone might have some pointers > since the kernel developers deal with so many patches. > > I've been given a massive kernel patch that makes a whole bunch of > conceptually independent changes. > > Does anyone have any advice on how to break it up into independent patches? dirdiff is a great tool for this. I think its on samba.org somewhere, but you can definitely find it in debian. The new version is even better, I think Paul should do a release :) Anton - 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/