public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Henrik Brix Andersen <brix@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Keys and words: ways to fail your team
Date: Wed, 29 Jun 2005 11:53:02 +0200	[thread overview]
Message-ID: <1120038782.12818.16.camel@sponge.fungus> (raw)
In-Reply-To: <623652d5050629024561bda9dc@mail.gmail.com>

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

On Wed, 2005-06-29 at 09:45 +0000, Chris Bainbridge wrote:
> Really? I thought the policy was "When upgrading, drop all existing
> keywords from arch to ~arch, and leave any existing ~arch keywords
> intact.".

It is.

Sincerely,
Brix
-- 
Henrik Brix Andersen <brix@gentoo.org>
Gentoo Metadistribution | Mobile computing herd

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

  reply	other threads:[~2005-06-29 10:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-28 22:41 [gentoo-dev] Keys and words: ways to fail your team Ilya A. Volynets-Evenbakh
2005-06-28 23:09 ` Peter Johanson
2005-06-28 23:30   ` Ilya A. Volynets-Evenbakh
2005-06-29  9:45     ` Chris Bainbridge
2005-06-29  9:53       ` Henrik Brix Andersen [this message]
2005-06-29 12:36       ` Mike Frysinger
2005-06-29 14:02     ` Chris Gianelloni

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=1120038782.12818.16.camel@sponge.fungus \
    --to=brix@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