From: Karel Zak <kzak@redhat.com>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Cc: Sami Kerola <kerolasa@iki.fi>,
Bernhard Voelker <mail@bernhard-voelker.de>,
util-linux@vger.kernel.org, Michael Cree <mcree@orcon.net.nz>
Subject: Re: Debian has not dropped alpha - was: Re: [PATCH] hwclock: stop supporting alpha cpu architecture
Date: Fri, 3 Aug 2018 12:46:34 +0200 [thread overview]
Message-ID: <20180803104634.xweogydpjklaece7@ws.net.home> (raw)
In-Reply-To: <7ad8126b-cc76-c341-d1c5-d9461f9c1f5f@physik.fu-berlin.de>
On Sat, Jul 28, 2018 at 01:01:45PM +0200, John Paul Adrian Glaubitz wrote:
> Hello!
>
> I was just pointed towards this mail and wanted to give a quick
> heads up! The original claim in the first mail is not accurate.
>
> While Debian has stopped supporting alpha **officially**, we are
> still supporting alpha in Debian Ports. In fact, Debian has more
> stable and working ports than Gentoo with many of them team-maintained
> by the Debian Ports team.
>
> For an overview of the currently supported targets, see:
>
> > https://buildd.debian.org/status/package.php?p=base-files&suite=sid
>
> All architectures build the vast majority of packages without problems
> and alpha is actually one of the healhiest ports with over 90% of
> all packages being built:
>
> > https://buildd.debian.org/stats/graph-ports-big.png
>
> Please do not drop support for alpha in util-linux.
This is misunderstanding. It's mostly about Alpha specific RTC stuff
like RTC_EPOCH_* ioctls rather than about Alpha as architecture.
I have reviewed the patch and it seems Sami is wrong. The current
kernel still supports these ioctls. So, NACK from my point of view.
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
prev parent reply other threads:[~2018-08-03 12:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-28 11:01 Debian has not dropped alpha - was: Re: [PATCH] hwclock: stop supporting alpha cpu architecture John Paul Adrian Glaubitz
2018-07-28 11:06 ` John Paul Adrian Glaubitz
2018-08-03 10:46 ` Karel Zak [this message]
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=20180803104634.xweogydpjklaece7@ws.net.home \
--to=kzak@redhat.com \
--cc=glaubitz@physik.fu-berlin.de \
--cc=kerolasa@iki.fi \
--cc=mail@bernhard-voelker.de \
--cc=mcree@orcon.net.nz \
--cc=util-linux@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).