Mark J. Nelson writes: > I think an upstream sync necessarily implies pulling the current upstream > source, integrating your changes, and building it OUTSIDE of the context > of ON. Anything else is negligent. Including the unused-in-ON code > provides no benefits that are immediately obvious to me.
+1. It creates an ever-increasing amount of flotsam in the gate, and thus a storage and time penalty that every single ON-based workspace must pay. It's waste with benefit to few -- and likely nobody at all. Having a single file called "upstream-excluded-unused.txt" with a list of such unneeded files would be fine. It'd help you during resync efforts (anything that appears to be new and isn't on that list is new stuff to look at and consider for inclusion if needed). Otherwise, please don't add lard. We've got plenty. -- James Carlson, Solaris Networking <[EMAIL PROTECTED]> Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 _______________________________________________ opensolaris-code mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
