public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Daniel Goller <morfic@gentoo.org>
To: gentoo-dev@robin.gentoo.org
Cc: gentoo-dev@robin.gentoo.org
Subject: Re: [gentoo-dev] Summary of PPC team meeting
Date: Sun, 20 Mar 2005 10:06:23 -0600	[thread overview]
Message-ID: <423D9F7F.2010103@gentoo.org> (raw)
In-Reply-To: <20050319205602.2b3bc787@snowdrop>

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

Ciaran McCreesh wrote:
> On Sat, 19 Mar 2005 21:34:02 +0100 Lars Weiler <pylon@gentoo.org> wrote:
> | That means, we will work an a common-profile with sub-profiles for ppc
> | and ppc64.  A first target-date would be the 2005.1 release.  The
> | masterplan[tm] for the team-merge should be presented at the next
> | meeting (in about four weeks).
>
> Is the ultimate aim a merged keyword like we did for sparc64 + sparc32
> -> sparc? If so, please don't use manson's script :)
>
> It'd be nice to see x86/amd64 going this way as well. I mean, we can fit
> mips under one keyword, and there's far more difference there than there
> is between a 386 and an opteron.
>
and i still can't see how amd64 devs would like to be lost in the void
that we call x86

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 256 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: Daniel Goller <morfic@gentoo.org>
To: gentoo-dev@gentoo.org
Cc: gentoo-dev@robin.gentoo.org
Subject: Re: [gentoo-dev] Summary of PPC team meeting
Date: Sun, 20 Mar 2005 10:06:23 -0600	[thread overview]
Message-ID: <423D9F7F.2010103@gentoo.org> (raw)
Message-ID: <20050320160623._LQGH-x4ZGaVC-8j3SmU9MoozteH8r-a89tvcse-Xmw@z> (raw)
In-Reply-To: <20050319205602.2b3bc787@snowdrop>

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

Ciaran McCreesh wrote:
> On Sat, 19 Mar 2005 21:34:02 +0100 Lars Weiler <pylon@gentoo.org> wrote:
> | That means, we will work an a common-profile with sub-profiles for ppc
> | and ppc64.  A first target-date would be the 2005.1 release.  The
> | masterplan[tm] for the team-merge should be presented at the next
> | meeting (in about four weeks).
>
> Is the ultimate aim a merged keyword like we did for sparc64 + sparc32
> -> sparc? If so, please don't use manson's script :)
>
> It'd be nice to see x86/amd64 going this way as well. I mean, we can fit
> mips under one keyword, and there's far more difference there than there
> is between a 386 and an opteron.
>
and i still can't see how amd64 devs would like to be lost in the void
that we call x86

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 256 bytes --]

  parent reply	other threads:[~2005-03-20 16:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-19 20:34 [gentoo-dev] Summary of PPC team meeting Lars Weiler
2005-03-19 20:56 ` Ciaran McCreesh
2005-03-19 21:06   ` Mike Frysinger
2005-03-19 21:12     ` Ciaran McCreesh
2005-03-19 21:52   ` Lars Weiler
2005-03-19 21:57     ` Ciaran McCreesh
2005-03-19 23:19       ` Brian Harring
2005-03-20 16:06   ` Daniel Goller [this message]
2005-03-20 16:06     ` Daniel Goller

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=423D9F7F.2010103@gentoo.org \
    --to=morfic@gentoo.org \
    --cc=gentoo-dev@gentoo.org \
    --cc=gentoo-dev@robin.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