Your message dated Sun, 22 Jun 2025 01:13:04 +0200
with message-id <afc8gjkar1drq...@per.namespace.at>
and subject line Re: Bug#930318: Suggestion for i386/amd64 "PC"
has caused the Debian Bug report #930318,
regarding Suggestion for i386/amd64 "PC"
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
930318: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930318
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release-notes
Severity: wishlist

Dear maintainers,

This would be almost about "already-done" in Debian community, as in,

Bug#575761: x86 architecture names are confusing

Where?
======

en/whats-new.dbk: "Supported architectures" section
1. 32-bit PC (i386) and 64-bit PC (amd64)
2. 64-bit ARM (arm64)

WHY?
====

* There are many "amd64" servers and "arm64" servers.
* There could be ARM PCs (starting with Windows 10 notebooks).
* To avoid "64 bit PC" could mean both amd64 and arm64.

Suggestion
----------

1. 32-bit x86 (i386) and 64-bit x86 (amd64)
2. 64-bit ARM (arm64)

In other words, I think, "PC" is not necessary now,
and a phrase "86" is alive since Intel released
their 8th gen. Core CPU "Core i7-8086K" in 2018.

Regards,

--- End Message ---
--- Begin Message ---
On Mon, Dec 23, 2024 at 02:53:51PM +0000, Richard Lewis wrote:
> The first message seems to be about adding(?) the term PC. I think
> that's a 1990s term which should not be used any more than it is today
> The last message asks for consistency with the kernel, which i think
> is the case today

Well, we do have "64-bit PC" in there now.

[..]
 
> I suggest we close this bug

Lets do that.

Chris

--- End Message ---

Reply via email to