All of lore.kernel.org
 help / color / mirror / Atom feed
From: Florian Fainelli <florian@openwrt.org>
To: sparclinux@vger.kernel.org
Subject: Re: debian unusable on niagara
Date: Mon, 04 May 2009 12:15:01 +0000	[thread overview]
Message-ID: <200905041415.01531.florian@openwrt.org> (raw)
In-Reply-To: <20090423.070943.158757350.davem@davemloft.net>

Hi,

Le Monday 04 May 2009 11:12:38 Josip Rodin, vous avez écrit :
> On Mon, May 04, 2009 at 09:40:26AM +0200, Julien Cristau wrote:
> > As far as I can tell, the main issue is that nobody's actively working
> > on the debian sparc port in the first place.  And without active
> > maintainers, that port is actually a disservice to users and the sparc
> > linux community.
>
> Even if nobody is currently volunteering to explicitly state that they are
> working on the port as a whole (which has always been a fairly vague
> concept anyway), the software is generally working fine (yes, even if it
> has bugs), the buildds are happily churning (and are actually actively
> maintained), new users do actually regularly come through, so I fail to see
> how it's a disservice to everyone.

A distribution developer should provide users with working kernels. Getting 
software x.y.z to work on sparc is something different. So rather than 
disservicing anyone it is just annoying not being able to boot a kernel or 
having it partially working for something as stupid as enabling/disabling the 
right kernel options.

>
> What is that statement supposed to mean, anyway? Would you prefer if
> the port didn't exist at all?

No as long as there are users for it, please maintain it, but focus your 
attention on kernels rather than geting the whole Debian package set to work.

My 2 cents.
-- 
Best regards, Florian Fainelli
Email : florian@openwrt.org
http://openwrt.org
-------------------------------

  parent reply	other threads:[~2009-05-04 12:15 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-23 14:09 debian unusable on niagara David Miller
2009-04-23 14:44 ` David Miller
2009-04-23 14:51 ` David Markey
2009-04-23 15:11 ` Andrew Robert Nicols
2009-04-27 22:29 ` Jurij Smakov
2009-04-28  1:41 ` David Miller
2009-04-28  7:54 ` Jurij Smakov
2009-04-28  7:56 ` David Miller
2009-04-28  7:57 ` David Miller
2009-04-28  8:09 ` Jurij Smakov
2009-04-28  8:44 ` David Miller
2009-05-02 10:25 ` Jurij Smakov
2009-05-02 10:28 ` Jurij Smakov
2009-05-02 16:53 ` David Miller
2009-05-02 17:04 ` Jurij Smakov
2009-05-02 20:14 ` David Miller
2009-05-02 20:56 ` Jurij Smakov
2009-05-02 21:26 ` David Miller
2009-05-02 22:54 ` Josip Rodin
2009-05-03  0:06 ` David Miller
2009-05-03 11:41 ` Josip Rodin
2009-05-03 13:35 ` Sam Ravnborg
2009-05-03 15:58 ` Josip Rodin
2009-05-03 16:02 ` Sam Ravnborg
2009-05-03 20:09 ` David Miller
2009-05-03 20:10 ` David Miller
2009-05-03 20:11 ` David Miller
2009-05-03 20:13 ` David Miller
2009-05-03 20:44 ` Josip Rodin
2009-05-03 20:50 ` David Miller
2009-05-04  7:40 ` Julien Cristau
2009-05-04  8:29 ` Josip Rodin
2009-05-04  9:12 ` Josip Rodin
2009-05-04  9:34 ` Julien Cristau
2009-05-04  9:57 ` Josip Rodin
2009-05-04 12:15 ` Florian Fainelli [this message]
2009-05-04 15:03 ` Josip Rodin
2009-05-04 16:55 ` David Miller
2009-05-04 16:58 ` David Miller
2009-05-04 17:33 ` Josip Rodin
2009-05-04 17:57 ` David Miller

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=200905041415.01531.florian@openwrt.org \
    --to=florian@openwrt.org \
    --cc=sparclinux@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.