-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Diego 'Flameeyes' Pettenò wrote: > On Sunday 24 April 2005 23:35, Ciaran McCreesh wrote: > >>They're >>supposed to do that for the first month or so (depending upon how long >>it is before it becomes obvious that you're safe). > > I was talking about double-checking *every* commit of every developer. That > will be an overkill, imho. >
I think if you limited it to commits that are essentially tree wide/eclasses it could be limited that way. Fex, this weekend there was a category move where repoman had some messed up behavior during the move causing mrness headaches with recommiting a bunch of crap. Things like this as well as eclass changes ( which have the potential to break 100's of ebuilds/packages ) would be decent coverage. As it stands right now someone can make a tree-wide commit and fsck crap up and the only recourse you have is to contact Infra and hope someone turns the cvs->rsync off in time. I think thats a glorious hack ( no offense brian, hehe ) of an otherwise obvious ( to me anyway ) problem. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iQIVAwUBQmwUr2zglR5RwbyYAQJHhA//UdfJnfSwpqWrs66Rf0efC917icoEcbbX AuT0ENAEoFw9QtgbNHY0+uZAL+iOrt7C5maxWa916bG9Zc5/qCSg87zeMSI02c+1 w9dcOpLhy48zVD+Tb7cctLztU+GAH9X+ZB7T7OuNnmz49CiZ/dW+wVDHEYiJzgSg btZ+1Thsuo1Lc4hiKCc+j/qW3y0igmc9vTmJElgYh4bzfyFvO/jXKR/oCrU4lghh kpdoJNR6oPH8od8P1PfdbQp1cHCcW8P3R3DbYE58O0M7rUtZRNUOkXtnPLV+t/E4 xSX59lNzIaUlrWVO0ImluKavLzoIpEU6OZzjQwxm+KFSv0mHx1Mk6/3Eu108hM/1 ze32sxHHRY4l+vlZGN8mySwIENcvlVFHbH+GJIdLbToFAZFvcB0FZ6xAeaPybdxJ /OlgvfzvN2viNnc3NZPmSOKCkljbZkcEiIg5TgeNX98UJV2gzQJEKOWuB3IjcNIb T0VwSmRiy0U8dfui53tL3lVF/XqgBA5j8F2oXR+btY7S0j5wSKW+msOzj05c8U8c 0A9209YURKh99J+5zXzffO6chHSlHiNJS19ME+5C3eAor78FJj3C0PlDXskO03p4 teco5foc4LbCQ4V+ACeGPRgctfV5j1BFCJxF5s3N4NWPK97DezVJgjC9UEatQGfz xdq1apDbe6Y= =XOel -----END PGP SIGNATURE----- -- gentoo-dev@gentoo.org mailing list
