-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 05/11/12 12:00 PM, Michael Orlitzky wrote: > > 1) Over time, unstable has become too stable (I know, I know). > People expect things to work, and nobody wants to break working > systems by committing works-in-progress to ~arch. >
We have p.mask for that, though, so dev's could get in the habit of committing and hard-masking things more, rather than using overlays. > The first I think could be helped with a third level of stability, > say, !arch, which stands for it-aint-gonna-fuckin-work-on-'arch'. well, per ~arch p.mask is possible here, as is removing keywords. For things that definitely don't work we also have '-arch' (usually used as -*) but that tends to be more permanent. Devs could > pile anything that's eventually headed for the tree here, and > catch conflicts early. I'm not entirely joking about the name -- it > would have to be clear that this is a staging area and no one > should use it in production. But this is a big change. - From p.mask'ing? *shrug* -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iF4EAREIAAYFAlCX9E4ACgkQ2ugaI38ACPD/BgD/cQgLXh8uE3hE0XziaeWzu5FZ hlPif1icqOvZkMMAvBYA/ig4YAtBSc0lTkIztnHKQYCh6gJPe9oOf2rJ7EZENvzR =J+Ib -----END PGP SIGNATURE-----
