I'll send a heads up, as Suha suggested. The regular expression fix will be part of a followup wad that will come from our project workspace, rather than a separate bug filed/putback before then. If any occurrences of "sccsget" (with no spaces) creep into the nightly.log/mail_msg, I'll bump that priority up appropriately.
--Mark On Mon, 14 Jul 2008, John Beck wrote: > Date: Mon, 14 Jul 2008 13:34:37 -0700 > From: John Beck <jbeck at eng.sun.com> > To: Mark J. Nelson <Mark.J.Nelson at Sun.COM> > Cc: ON NV Gatekeeping Team <gatekeeper at onnv.eng.sun.com>, > scm-migration-dev at opensolaris.org > Subject: Re: [scm-migration-dev] soliciting opinions on sccs noise > > Mark> So now we're three weeks away from Mercurial, and I need direction from > Mark> the ON NV core team. Do I: > > Mark> 1. Leave it the way it is, allowing SCCS Noise into nightly mail_msgs, > Mark> knowing that we're about to get rid of Teamware usage anyway. > > Mark> 2. Turn SCCS Noise into a transient, such that it only appears in > Mark> mail_msg when it changes. > > Mark> 3. Revert the regular expression, knowing that it won't catch valid SCCS > Mark> noise. > > Mark> 4. Fix the regular expression, leaving us still needing to decide > Mark> between options 1 and 2 above. > > Mark> 5. Something else? > > I think a 4+1 approach makes the most sense: fix the regular expression, but > leave the SCCS noise since we're about to get rid of Teamware anyway. > > -- John > > http://blogs.sun.com/jbeck >
