Date: Tue, 28 May 2002 19:13:12 +1000 From: "Chris Knight" <chris@aims.com.au> To: <freebsd-hackers@freebsd.org> Subject: Maintaining Large Patchsets Against FreeBSD Message-ID: <001101c20627$e70941f0$020aa8c0@aims.private>
next in thread | raw e-mail | index | archive | help
Howdy, I'm currently maintaining a largish (~4MB) patchset against FreeBSD 4.x releases. Due to the nature of the patches, they'll never make it into the FreeBSD tree. I currently maintain the patchset by checking out the previous 4.x release, applying the patchset, doing a cvs update and resolving the conflicts. I then add any additional patches and then cat up all the diffs in the tree. I was wondering if this was the most optimal way of maintaining the patchset? The other approach I can see would be to create my own repository and import the FreeBSD release code into my repository and then resolve the conflicts. This would then give me better historical code management. Any suggestions would be useful. Regards, Chris Knight Systems Administrator AIMS Independent Computer Professionals Tel: +61 3 6334 6664 Fax: +61 3 6331 7032 Mob: +61 419 528 795 Web: http://www.aims.com.au To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?001101c20627$e70941f0$020aa8c0>