-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Justin Mason wrote: > Theo Van Dinter writes: >> On Thu, Aug 02, 2007 at 05:54:18PM +0100, Justin Mason wrote: >>> as far as I know, if they're rules in the "rulesrc" tree, it's >>> C-T-R; but rules in the "rules" dir are still R-T-C. >>> >>> I'd be happy to loosen this up, though. >> I'm fine with that too. The rules dir (imo) is essentially a snapshot of the >> rules in the update channel at the time, so I don't see much reason to have >> them not both be CTR. > > ok, let's vote to change the procedure: that changes in the "rules" tree > be considered Commit-Then-Review, even when changes in the code (such as > "lib") are considered Review-Then-Commit. > > My vote: +1 > > --j.
+1 for this from me as well. "Rules is Rules" (Wonders is someone will get my quote?) - -- -Doc Penguins: Do it on the ice. 8:44am up 4 days, 16:55, 17 users, load average: 0.18, 0.30, 0.37 SARE HQ http://www.rulesemporium.com/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with CentOS - http://enigmail.mozdev.org iD8DBQFGshu8qOEeBwEpgcsRAvfCAKCGQ4vmVVrC23Qs1Yf7yjbiyY6ylQCdE2i/ do00I4Jh05ANz+QkEijjuog= =hKsx -----END PGP SIGNATURE-----
