Alexander Kuzmin writes: > Because int this case it would be probably closed as a duplicate of this > solved problem. If you think that's an incorrect procedure, I'll file a > new CR and can cite you in the comments, in case the bug gets closed as > a duplicate.
Please do. Having multiple putbacks of the same CR into separate marketing releases makes no sense and just makes a hash of the SCCS history. It's just not done. At least in ON, MRs are used for backports, not as a means to signify a "lazarus" bug in a new marketing release. Your new CR should (if possible) explain why the original fix was wrong, incomplete, didn't fix the problem, or somehow came undone over time. You might also add the "lazarus" keyword if it has in fact come back even though it was once fixed. If you don't want to take my word for it, check with the ON gatekeepers. -- 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-discuss mailing list [EMAIL PROTECTED]
