On Sun, 9 May 2004, Arkady V.Belousov wrote: > Hi! > > 9-���-2004 15:39 [EMAIL PROTECTED] (Bart Oldeman) wrote to > [EMAIL PROTECTED]: > > BO> See for instance > BO> * From: Arkady V.Belousov > BO> * Subject: [Freedos-kernel] patch: mix > BO> * Date: Sat, 24 Apr 2004 01:56:11 -0700 > BO> Arkady, you should split this patch in 20 easily digestible chunks, and I > BO> will apply about 3 of them. If you don't want to split it, fine, the patch > BO> just goes to NUL. > > How? See: > > - in intr.asm changed allocmem(). > - to allocmem() relate changes in init-mod.h and config.c.
So you prepare one logical chunk that touches intr.asm, init-mod.h and config.c. You can do that as follows: apply logical change, diff with previous apply next logical change diff with previous this is fine with me. What you first of all need to do is to isolate the bug fixes from all other changes. Then one patch is one bugfix. Overlapping usually isn't a big problem; "patch" can use a certain amount of fuzziness to deal with that -- I will just see a reject if it fails the fuzzy logic and can then deal with it manually. You should explicitly state it if patch Y really depends on patch X to apply. The main idea is to submit multiple *logical* changes with a short description about what each change does. Bart ------------------------------------------------------- This SF.Net email is sponsored by Sleepycat Software Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver higher performing products faster, at low TCO. http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3 _______________________________________________ Freedos-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freedos-devel
