On Tue, Oct 08, 2002 at 04:10:42PM -0700, Peter Wemm wrote: > "David O'Brien" wrote: > > On Tue, Oct 08, 2002 at 03:55:36PM -0400, John Baldwin wrote: > > > Could you please just commit this on the vendor branch if it is the > > > vendor fix for now. Since the next vendor import will contain the > > > fix you don't need to worry about maintaining the local patch so > > > committing it onto the vendor branch is ok. > > > > Doing this screws up diffs to vendor source as there won't be a tag that > > corisponds with this across all files. For small contribed things that > > is OK. But when doing large ones it the following import+merge becomes > > harder. > > While that is true, it usually isn't all that big a deal if you are careful > and keep track of what you've done. It is certainly better than causing > the file to leave the vendor branch for something you *know* is now in the > vendor tree. And I think its better than leaving a known 'compiler crash' > case there to bite developers.
I'm hoping for another 3.2.1 import soon. I raised some hell on the GCC lists last week about the quality of 3.2.1; and actually got some Athlon and p4 optimization PR's taken care of. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
