Breaking up a monolithic patch

[Florent Thoumie]

Le Mardi 07 juin 2005 à 12:50 -0700, Loren M. Lang a écrit :
> I have been working on porting Cinelerra to freebsd and I currently have
> one large monolithic patch that will make cinelerra compile and run on
> freebsd.  Now I am trying to figure out how to break it up.  It looks
> like the simplest method would be to break it up for each file that's
> modified, then I could use the existing update-patches framework to
> maintain it.  But I think the better solution would be to break it up
> functionally, though it's harder to maintain.  I could make a series of
> patches to be applied in order, where one patch would modify cinelerra
> to have a customizable prefix, another would disable the linux firewire
> support.  This approach would make several patches that will overlap
> some and touch some of the same files, but it would be more useful in
> the long run.  It would be easy to see what was modified to disable
> firewire and figure out how to update it to use the freebsd firewire
> support instead of disabling it.  If I do this though, I'll probably
> need to spend some time making a script to help generate the patches
> appropriately.

	Use Tools/scripts/splitpatch force !

-- 
Florent Thoumie
flz at xbsd.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: This is a digitally signed message part
Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20050608/f7655ac9/attachment.bin