public inbox for gentoo-releng@lists.gentoo.org
 help / color / mirror / Atom feed
From: Lars Weiler <pylon@gentoo.org>
To: ppc64@gentoo.org, ppc@gentoo.org
Cc: gentoo-releng@lists.gentoo.org
Subject: Re: [gentoo-releng] Re: ppc outlines for the release
Date: Wed, 6 Jul 2005 09:17:38 +0200	[thread overview]
Message-ID: <20050706071738.GL31682@celeborn.wh-og.hs-niederrhein.de> (raw)
In-Reply-To: <1120630796.7841.15.camel@amd64.anyarch.net>

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

* Daniel Ostrow <dostrow@gentoo.org> [05/07/06 02:19 -0400]:
> The new profiles are in and all under
> default-linux/ppc/2005.1/{ppc,ppc64}. Check them out while they are
> still hot.

Cool, thanks!

[...]
> considering making something as popular as the G5 stages multilib only,
> chances are that there will be both 32 and 64-bit userland releases.

Good.  That means I don't need a G5-32bit-Kernel, as this
processor will be provided by the ppc64-team completely.

> Regarding ppc32 I see the following as a good target:
> 
> Generic ppc32 stage1
> Generic ppc32 stage2
> G4 stage2
> Generic ppc32 stage3
> G4 stage3
> Pegasos stage3

I'm fine with that.  Pegasos has only changes in the virtual
and packages.  That means, it is usually the same like G4,
but without some Applec-specific stuff.

Regards, Lars

-- 
Lars Weiler  <pylon@gentoo.org>  +49-171-1963258
Gentoo Linux PowerPC    : Developer and Release Engineer
Gentoo Infrastructure   : CVS Administrator
Gentoo Foundation       : Trustee

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

      reply	other threads:[~2005-07-06  7:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-05 22:45 [gentoo-releng] ppc outlines for the release Lars Weiler
2005-07-06  6:19 ` [gentoo-releng] " Daniel Ostrow
2005-07-06  7:17   ` Lars Weiler [this message]

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=20050706071738.GL31682@celeborn.wh-og.hs-niederrhein.de \
    --to=pylon@gentoo.org \
    --cc=gentoo-releng@lists.gentoo.org \
    --cc=ppc64@gentoo.org \
    --cc=ppc@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