public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Robert Bridge <robert@robbieab.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev]  Re: [RFC] New keywords for non-Gentoo Linux platforms
Date: Fri, 10 Oct 2008 17:13:38 +0100	[thread overview]
Message-ID: <20081010171338.53e37deb@pheonix> (raw)
In-Reply-To: <20081010175637.1e5e0b5e.genone@gentoo.org>

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

On Fri, 10 Oct 2008 17:56:37 +0200
Marius Mauch <genone@gentoo.org> wrote:

> On Fri, 10 Oct 2008 14:48:19 +0200
> Fabian Groffen <grobian@gentoo.org> wrote:
> 
> > Whatever.  Some of you seem to have some quite agressive dislikement
> > to it.  In the end it's just a name/tag.  I guess I could live with
> > anything, including c3p0.
> 
> Well, while I dislike x64 I'm more concerned about using different
> names (amd64 and x64) for the same architecture (same would apply if
> you had used i386 or ia32 in some cases instead of x86) and was just
> checking if there was any functional reason for that difference.

I would agree with this.

As a user coming to the project, x64 is NOT the same arch as amd64, it
has a different name! Select one name for the arch, and use it
everywhere. Consistent naming is more important than having the name
absolutely technically correct.

And seeing as Gentoo uses amd64 for all those arches in the main tree
with minimal problems, I personally would vote for using amd64 in -alt
to retain consistency with the rest of Gentoo.

Just my 2 cents.

Rob.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2008-10-10 16:13 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-09 18:11 [gentoo-dev] [RFC] New keywords for non-Gentoo Linux platforms Fabian Groffen
2008-10-09 22:05 ` Marius Mauch
2008-10-10  0:16   ` [gentoo-dev] " Duncan
2008-10-10  2:21     ` Marius Mauch
2008-10-10  7:15       ` Fabian Groffen
2008-10-10 12:40         ` Diego 'Flameeyes' Pettenò
2008-10-10 12:48           ` Fabian Groffen
2008-10-10 15:56             ` Marius Mauch
2008-10-10 16:13               ` Robert Bridge [this message]
2008-10-10 15:21         ` Ryan Hill
2008-10-10  8:56 ` [gentoo-dev] " Michael Haubenwallner
2008-10-10 12:56 ` Jeremy Olexa
2008-10-13  5:16   ` [gentoo-dev] " Steve Long
2008-10-13 14:27     ` Ciaran McCreesh
2008-10-13 17:59       ` Fabian Groffen
2008-10-14  7:48         ` Michael Haubenwallner
2008-10-15 10:20           ` [gentoo-dev] " Steve Long
2008-10-17 14:22 ` [gentoo-dev] " Michael Haubenwallner
2008-10-21 14:09   ` [gentoo-dev] " Tiziano Müller
2008-10-21 19:01     ` Fabian Groffen

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=20081010171338.53e37deb@pheonix \
    --to=robert@robbieab.com \
    --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