From: Ralf Baechle <ralf@linux-mips.org>
To: Florian Lohoff <f@zz.de>
Cc: linux-mips@linux-mips.org
Subject: Re: Fwd: Roll call for porters of architectures in sid and testing (Status update)
Date: Thu, 19 Sep 2013 15:58:52 +0200 [thread overview]
Message-ID: <20130919135852.GB22468@linux-mips.org> (raw)
In-Reply-To: <20130919103158.GB7476@pax.zz.de>
On Thu, Sep 19, 2013 at 12:31:58PM +0200, Florian Lohoff wrote:
> just a heads up that Mips and Mipsel are 2 architectures in danger
> of beeing dropped by Debian if no one steps up as a porter beeing
> reachable for addressing architecture specific bugs.
What components and packages are we talking about? Are we talking about
a fulltime job for a small army of geeks or?
> No need to be DD
Good, I don't do dungeons and dragons!
Ralf
next prev parent reply other threads:[~2013-09-19 13:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-19 10:31 Fwd: Roll call for porters of architectures in sid and testing (Status update) Florian Lohoff
2013-09-19 13:58 ` Ralf Baechle [this message]
2013-09-19 14:10 ` Florian Lohoff
2013-09-19 14:54 ` Ralf Baechle
2013-09-19 15:07 ` Florian Lohoff
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=20130919135852.GB22468@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=f@zz.de \
--cc=linux-mips@linux-mips.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