[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Unattended issues

From: Thomas Schwinge
Subject: Re: Unattended issues
Date: Sun, 28 Aug 2005 02:21:25 +0200
User-agent: Mutt/1.5.9i

On Sat, Aug 27, 2005 at 02:09:13PM -0700, Thomas Bushnell BSG wrote:
> Thomas Schwinge <schwinge-lists-gnu.org-bug-hurd@nic-nac-project.de> writes:
> > It's very unfortunate for developers that are not (yet ?) that intimate
> > with the Hurd and GNU Mach that there is nearly no one available to be
> > asked about e.g. design issues; things that are more tricky than fixing
> > simple bugs, etc.
> Please ask, if there are questions.

Questions have been asked on this mailing list, for example those whose
headers I just quoted in my previous message.
A few examples were give in the first message of this very thread:

| <URL:http://lists.gnu.org/archive/html/bug-hurd/2005-08/msg00076.html>
| <URL:http://lists.gnu.org/archive/html/bug-hurd/2005-07/msg00278.html>
| <URL:http://lists.gnu.org/archive/html/bug-hurd/2005-08/msg00065.html>
| <URL:http://lists.gnu.org/archive/html/bug-hurd/2005-08/msg00069.html>

is another one.

> Most questions amount to "please
> explain everything" or "give me a tour of the source", which are hard
> to answer.

That's of course true.  Nobody expects you to answer those; at least I
don't expect that.

> Specific questions ("why was it designed this way?" "how
> should that work?") much more frequently get replies.

Hm.  Really?  Sometimes they do, but often enough they don't.

> > It's also very unfortunate that the Hurd is being forked without
> > discussing (or reporting, at least) that on this very mailing list.
> Which fork are you referring to?

The one whose URL I just gave in my previouse message:
That fork stalled in the meantime, due to Alfred's intervention.
(Without any valuation.)

Shall it really be common practice that you (the maintainers) have to be
CCed for every (sensible) question?
Don't you read the mailing list(s)?
(Those are questions, not criticisms.)


reply via email to

[Prev in Thread] Current Thread [Next in Thread]