From: Dirkjan Ochtman <djc@gentoo.org>
To: Gentoo Development <gentoo-dev@lists.gentoo.org>
Cc: perl@gentoo.org
Subject: Re: [gentoo-dev] About m68k arch status in perl packages
Date: Wed, 26 Jun 2013 21:35:18 +0200 [thread overview]
Message-ID: <CAKmKYaDRF1MEocWNs3GfeeJ9KEhgDbJdG9XU29sHSRqNk5KM4w@mail.gmail.com> (raw)
In-Reply-To: <51CB39CC.7090609@gentoo.org>
On Wed, Jun 26, 2013 at 8:58 PM, Mikle Kolyada <zlogene@gentoo.org> wrote:
> Hi all. We have very long delay with m68k arch in many stabilization
> bugs, especially in perl-related. I think this is not ok. The only one
> mk68k developer is vapier, so i want say: if we'll have no progress in
> stabilization for m68k for a two weeks, i'll close all bugs, that have
> m68k as last arch (i have no hardware to test it) and drop related
> keyword in package to unstable.
IIRC we've had discussions in the past about making m68k permanently
~arch-only, like mips.
Cheers,
Dirkjan
prev parent reply other threads:[~2013-06-26 19:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-26 18:58 [gentoo-dev] About m68k arch status in perl packages Mikle Kolyada
2013-06-26 19:35 ` Dirkjan Ochtman [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=CAKmKYaDRF1MEocWNs3GfeeJ9KEhgDbJdG9XU29sHSRqNk5KM4w@mail.gmail.com \
--to=djc@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=perl@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