util-linux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: Sami Kerola <kerolasa@iki.fi>
Cc: Bernhard Voelker <mail@bernhard-voelker.de>,
	Karel Zak <kzak@redhat.com>,
	util-linux@vger.kernel.org, Michael Cree <mcree@orcon.net.nz>
Subject: Debian has not dropped alpha - was: Re: [PATCH] hwclock: stop supporting alpha cpu architecture
Date: Sat, 28 Jul 2018 13:01:45 +0200	[thread overview]
Message-ID: <7ad8126b-cc76-c341-d1c5-d9461f9c1f5f@physik.fu-berlin.de> (raw)

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.

To get in touch with us, we're hanging around in #debian-ports on OFTC.

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaubitz@debian.org
`. `'   Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
  `-    GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

             reply	other threads:[~2018-07-28 11:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-28 11:01 John Paul Adrian Glaubitz [this message]
2018-07-28 11:06 ` Debian has not dropped alpha - was: Re: [PATCH] hwclock: stop supporting alpha cpu architecture John Paul Adrian Glaubitz
2018-08-03 10:46 ` Karel Zak

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=7ad8126b-cc76-c341-d1c5-d9461f9c1f5f@physik.fu-berlin.de \
    --to=glaubitz@physik.fu-berlin.de \
    --cc=kerolasa@iki.fi \
    --cc=kzak@redhat.com \
    --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).