public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Chris Gianelloni <wolf31o2@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Security/QA Spring Cleaning
Date: Wed, 24 May 2006 08:06:30 -0400	[thread overview]
Message-ID: <1148472390.11657.4.camel@vertigo.twi-31o2.org> (raw)
In-Reply-To: <4473DCE4.3080106@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 477 bytes --]

On Wed, 2006-05-24 at 00:11 -0400, Doug Goldstein wrote:
> My opinion is "snap, crackle, and pop"... let the tree break. But better
> yet... figure out what depends on package X <=1.0 and p.mask it.

Umm... anything that depends on the package in question *should* be
getting masked.  There's no opinion to it.  Breaking the tree is a
definite no-no.

-- 
Chris Gianelloni
Release Engineering - Strategic Lead
x86 Architecture Team
Games - Developer
Gentoo Linux

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2006-05-24 12:16 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-22  3:02 [gentoo-dev] Security/QA Spring Cleaning Ned Ludd
2006-05-22  5:25 ` Robin H. Johnson
2006-05-22  5:30   ` Brian Harring
2006-05-23 20:22 ` Ned Ludd
2006-05-23 20:44   ` Brian Harring
2006-05-23 22:44     ` Thomas Cort
2006-05-23 20:51   ` Chris Gianelloni
2006-05-23 21:06     ` Brian Harring
2006-05-23 21:46       ` Chris Gianelloni
2006-05-23 22:05         ` Brian Harring
2006-05-23 22:24           ` Chris Gianelloni
2006-05-23 22:36             ` Brian Harring
2006-05-24  4:11               ` Doug Goldstein
2006-05-24 12:06                 ` Chris Gianelloni [this message]
2006-05-24 12:02               ` Chris Gianelloni
2006-05-23 21:50     ` Ned Ludd
2006-05-23 22:22       ` Chris Gianelloni
2006-05-28 18:20   ` Ned Ludd
2006-05-28 20:18     ` Robin H. Johnson
2006-05-29  1:17       ` Ned Ludd
2006-05-29 20:22     ` Chris Gianelloni
2006-06-02 13:15     ` Eldad Zack

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1148472390.11657.4.camel@vertigo.twi-31o2.org \
    --to=wolf31o2@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox