public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andreas Dilger <adilger@clusterfs.com>
To: Chris Friesen <cfriesen@nortelnetworks.com>
Cc: "Martin J. Bligh" <mbligh@aracnet.com>,
	Anton Blanchard <anton@samba.org>,
	Linux kernel <linux-kernel@vger.kernel.org>,
	paulus@samba.org
Subject: Re: offtopic: how to break huge patch into smaller independent patches?
Date: Tue, 14 Sep 2004 19:47:11 -0600	[thread overview]
Message-ID: <20040915014711.GA30607@schnapps.adilger.int> (raw)
In-Reply-To: <414799D1.7050609@nortelnetworks.com>

On Sep 14, 2004  19:24 -0600, Chris Friesen wrote:
> >If the changes are in fairly independant files, just vi'ing the diff is
> >normally very effective. If they're all intertangled, then starting again
> >from scratch is prob easier ;-)
> 
> Unfortunately I've got over 550 files being changed, in probably about 50 
> conceptual areas.

Start with the smallest logical change(s), possibly just extracting them
from the big diff with vi.  Assuming you have a decent diff format (-up
is what I find the most useful) you should just be able to copy the
original patch, delete all the hunks that are unrelated, and you are left
with logical change.

Now that you have it as a separate patch, apply it to the reference tree
and rediff to get a reduced-size combined patch.  For some changes that
stomp on overlapping lines of code you don't have much hope but to recreate
them by hand, but hopefully those are in relatively few areas.

Consider using a source-control tool next time ;-/.  

Cheers, Andreas
--
Andreas Dilger
http://sourceforge.net/projects/ext2resize/
http://members.shaw.ca/adilger/             http://members.shaw.ca/golinux/


  reply	other threads:[~2004-09-15  1:47 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-14 19:48 offtopic: how to break huge patch into smaller independent patches? Chris Friesen
2004-09-14 20:11 ` William Lee Irwin III
2004-09-14 20:12 ` Dave Jones
2004-09-14 22:12   ` J. Bruce Fields
2004-09-16 21:11   ` Matthias Urlichs
2004-09-16 21:21     ` Herbert Poetzl
2004-09-15  0:20 ` Anton Blanchard
2004-09-15  0:47   ` Martin J. Bligh
2004-09-15  1:24     ` Chris Friesen
2004-09-15  1:47       ` Andreas Dilger [this message]
2004-09-15  4:36         ` Chris Friesen
2004-09-15  5:27           ` Martin J. Bligh
2004-09-15 11:48             ` Arnd Bergmann
2004-09-15 23:05           ` Andrew Morton

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20040915014711.GA30607@schnapps.adilger.int \
    --to=adilger@clusterfs.com \
    --cc=anton@samba.org \
    --cc=cfriesen@nortelnetworks.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mbligh@aracnet.com \
    --cc=paulus@samba.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox