Thomas Schwinge <[EMAIL PROTECTED]> writes:

> Questions have been asked on this mailing list, for example those whose
> headers I just quoted in my previous message.

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

This is not a question; it is a libc patch.

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

I see no question about the Hurd here.  What I see is a
feature-extension request for Mach, together with a partial interface
specification. 

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

I see no question here.  This is a bug, not a question, and I for one
see no problem with the patch proposed.  I am not, however, the one
who checks in changes to the Hurd source these days.

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

I see no question here.  As for the change suggested, I would want to
see some research on how this patch performs in practice.

> <URL:http://lists.gnu.org/archive/html/bug-hurd/2004-12/msg00242.html>

I see no question here.  I see a feature extension request for Mach.

So, to sum up, if you have a question about design, ask a question.
Questions are in the interrogative mood, come complete with question
marks, and so forth.

Requests for feature extensions, bug fixes, and the like, are not the
same thing as questions.  

>> 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.

Please, example?

> 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.)

I do read the mailing lists; I use gnus with sensible
nnmail-split-fancy, so anything CCed to me will simply land in the
same place that it would without.

When I see a patch, I do not answer it if there is no question.

Thomas



_______________________________________________
Bug-hurd mailing list
Bug-hurd@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-hurd

Reply via email to