From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31237 invoked from network); 3 Sep 2004 17:07:42 +0000 Received: from smtp.gentoo.org (156.56.111.197) by lists.gentoo.org with AES256-SHA encrypted SMTP; 3 Sep 2004 17:07:42 +0000 Received: from lists.gentoo.org ([156.56.111.196] helo=parrot.gentoo.org) by smtp.gentoo.org with esmtp (Exim 4.34) id 1C3HXK-0004aR-FC for arch-gentoo-dev@lists.gentoo.org; Fri, 03 Sep 2004 17:07:42 +0000 Received: (qmail 18511 invoked by uid 89); 3 Sep 2004 17:07:41 +0000 Mailing-List: contact gentoo-dev-help@gentoo.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Received: (qmail 8065 invoked from network); 3 Sep 2004 17:07:41 +0000 Date: Fri, 3 Sep 2004 17:07:40 +0000 From: Kurt Lieber To: Lisa Seelye Cc: Gentoo Dev Message-ID: <20040903170740.GN23171@mail.lieber.org> References: <1094227795.20758.37.camel@lisa.thedoh.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="lJhfsPy4o8B7pjPr" Content-Disposition: inline In-Reply-To: <1094227795.20758.37.camel@lisa.thedoh.com> X-GPG-Key: http://www.lieber.org/kurtl.pub.gpg User-Agent: Mutt/1.5.6i Subject: Re: [gentoo-dev] Should significant changes to arch be posted to -announce mail list? X-Archives-Salt: 40701d64-620d-48ff-9d07-fcad52adc7b8 X-Archives-Hash: 38d0c154241dff74b09614f3919b6f5f --lJhfsPy4o8B7pjPr Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline On Fri, Sep 03, 2004 at 12:09:55PM -0400 or thereabouts, Lisa Seelye wrote: > I think they should. Having new blockers come up on an arch box when > attempting to update is a little worrysome. Or having a new way of > doing things (such as the inevitable move to udev in lieu of devfs). I agree with ciaran. I don't really care if there's a blocker on mips, arm, sparc, etc. and I don't want to have to read about those problems. Similarly, I'm sure sparc users don't care about x86 problems. In short, let's post arch-specific issues to the appropriate arch list. --kurt --lJhfsPy4o8B7pjPr Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFBOKTcJPpRNiftIEYRAiUqAJ9Dtwc3H4g5T0qmASYO5xSboI3eAwCfRXSJ 45xcXz+DtRGnODIUrUOXt38= =ihit -----END PGP SIGNATURE----- --lJhfsPy4o8B7pjPr--