On Tue, Dec 9, 2008 at 10:11 PM, Les Mikesell <lesmikesell@xxxxxxxxx> wrote: > Known-bad in this scenario means detected after the initial rollout but > before the end of the window to the next 'new code' push. Being able to > avoid those and get the fixed version instead on your critical machines > would make using fedora a lot more practical. Where do you collect and store the information that marks an update as known bad? -jef -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list