Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S269727AbUINTxf (ORCPT ); Tue, 14 Sep 2004 15:53:35 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S269757AbUINTuu (ORCPT ); Tue, 14 Sep 2004 15:50:50 -0400 Received: from zcars04f.nortelnetworks.com ([47.129.242.57]:25002 "EHLO zcars04f.nortelnetworks.com") by vger.kernel.org with ESMTP id S269367AbUINTss (ORCPT ); Tue, 14 Sep 2004 15:48:48 -0400 Message-ID: <41474B15.8040302@nortelnetworks.com> Date: Tue, 14 Sep 2004 13:48:37 -0600 X-Sybari-Space: 00000000 00000000 00000000 00000000 From: Chris Friesen User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040113 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Linux kernel Subject: offtopic: how to break huge patch into smaller independent patches? Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 561 Lines: 16 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? Chris - 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/