Some history revisionism has taken place in the src/contrib area as part of making way for the next gcc update.
Do not be alarmed when you see your next cvsup output (in cvs mode, not -checkout mode). I am aware of a couple of minor problems, but I dont think they break anything But if something (eg: cvs, cvsup, etc) does break, I need to know about it. cvs or cvsup doing 'fixups' or reporting checksum errors is expected and should only happen once. ie: it should be recovered from automaticaly and NOT happen next time. I only want to know if: - something is corrupted - cvs or cvsup or some other tool crash or report persistant errors - source is corrupted, particularly in RELENG_4. Yes, there are some intentional differences between gcc and gcc.295 etc due to some commits being deliberately left out. Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message