public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Christian Bricart <christian@bricart.de>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: Arch Status and Future Plans
Date: Wed, 26 Jun 2024 10:29:49 +0200	[thread overview]
Message-ID: <efd87a30-ff86-4104-9540-0776c07b711b@bricart.de> (raw)
In-Reply-To: <a30daaac-d1c5-46ca-b1f0-63db08a8d7de@gentoo.org>

Am 26.06.24 um 09:38 schrieb Florian Schmaus:
> Hi Arthur,
> 
> thanks for taking the time to write this mail.
> 
> On 25/06/2024 19.33, Arthur Zamarin wrote:
>> ======== x86 ========
>>
>> Stable 32-bit arch. I'll be honest, I don't believe at all this should
>> be stable arch anymore.
> 
> I have the impression as well. The time to drop stable keywords for x86 
> probably has come. But I always wonder if there is a x86 use-case we are 
> not aware of. Therefore, if there is a group of x86 Gentoo users out 
> there, then they should speak now and ideally elaborate a bit on their 
> use case.

well - at least *I* am running x86 on a bunch of Intel Atom boards 
(-march=bonnell, "Diamondville") which are mostly purposed as routers, 
but also keeping some of those early "Netbooks" based on that processor 
alive.
All equipped with (the platform's max of) 2 Gi RAM, they still suit 
their purpose well…

Cheers
   Christian


  reply	other threads:[~2024-06-26  8:30 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-25 17:33 [gentoo-dev] Arch Status and Future Plans Arthur Zamarin
2024-06-25 21:40 ` matoro
2024-06-25 22:55 ` James Le Cuirot
2024-06-26  0:06 ` Notion of stable depgraph vs stable keywords (Re: [gentoo-dev] Arch Status and Future Plans) Sam James
2024-06-28  4:17   ` [gentoo-dev] Re: Notion of stable depgraph vs stable keywords (Re: " Duncan
2024-06-28  5:16     ` Sam James
2024-06-26  0:14 ` Misc arch plans (Re: [gentoo-dev] " Sam James
2024-06-26 20:29   ` ia64, was: " Andreas K. Huettel
2024-06-26 20:45     ` matoro
2024-06-26  0:17 ` On the value (or not?) of stable keywords " Sam James
2024-06-26  0:19 ` time64 & LFS for 32-bit arches " Sam James
2024-06-26  0:20 ` x86 FP issues " Sam James
2024-06-28  5:20   ` Michał Górny
2024-06-26  7:38 ` [gentoo-dev] Re: Arch Status and Future Plans Florian Schmaus
2024-06-26  8:29   ` Christian Bricart [this message]
2024-06-26 20:44   ` Immolo
2024-06-26 19:47 ` nomenclature, was: Re: [gentoo-dev] " Andreas K. Huettel
2024-06-26 20:18 ` Andreas K. Huettel
2024-06-26 20:24 ` riscv, was: " Andreas K. Huettel
2024-06-26 21:08 ` 32bit vs 64bit, " Andreas K. Huettel
2024-06-28 16:12 ` splitting keywords, " Andreas K. Huettel

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=efd87a30-ff86-4104-9540-0776c07b711b@bricart.de \
    --to=christian@bricart.de \
    --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