From: "Andreas K. Huettel" <dilfridge@gentoo.org>
To: Arthur Zamarin <arthurzam@gentoo.org>, gentoo-dev@lists.gentoo.org
Cc: gentoo-dev@lists.gentoo.org, Sam James <sam@gentoo.org>
Subject: ia64, was: Re: Misc arch plans (Re: [gentoo-dev] Arch Status and Future Plans)
Date: Wed, 26 Jun 2024 22:29:33 +0200 [thread overview]
Message-ID: <46472341.fMDQidcC6G@pinacolada> (raw)
In-Reply-To: <87bk3opnks.fsf@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 657 bytes --]
> > ======== ia64 ========
> >
> > Dev 64-bit arch. Kernel dropped support, glibc dropped support, devbox
> > died - days are short before full exp status or full removal of arch.
>
> Yeah, no interest in ia64, sorry. I'd like it to just go.
This is probably unavoidable given that our devbox and stage builder is unstable
now regularly dies (and that there is also no qemu support).
I'm all for keeping what we can, but we need
* people to do the work
* hardware to test
If *both* is missing it's kinda hopeless.
--
Andreas K. Hüttel
dilfridge@gentoo.org
Gentoo Linux developer
(council, toolchain, base-system, perl, libreoffice)
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 981 bytes --]
next prev parent reply other threads:[~2024-06-26 20:29 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 ` Andreas K. Huettel [this message]
2024-06-26 20:45 ` ia64, was: " 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
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=46472341.fMDQidcC6G@pinacolada \
--to=dilfridge@gentoo.org \
--cc=arthurzam@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=sam@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