Hurd-devel -- Developers discussion list for GNU Hurd

 

About Hurd-devel
English (USA)

Closed list. The archives are public.

You cannot subscribe to this list. You'll be invited when time is due. Please subscribe to the hurd-devel-readers list instead, which is a read-only mirror of this list.



This list is for detailed discussions of design and implementation issues in the GNU Hurd. Its membership is limited to experienced Hurd developers so that we can keep our discussions on track and concise given the limited time the senior developers have to contribute. The archives of this list are public and we encourage anyone interested in Hurd hacking to read up on all the past and current discussions. The list membership is private for efficiency of discussion and not to exclude serious new participants. We encourage people starting out with the Hurd to carry on all their discussions on the help-hurd, bug-hurd, and debian-hurd mailing lists as appropriate. We look forward to welcoming more hackers onto the hurd-devel list as they gain experience with the Hurd and start to contribute their insights to our design thinking.


To see the collection of prior postings to the list, visit the Hurd-devel Archives.

Using Hurd-devel
To post a message to all the list members, send email to hurd-devel@gnu.org.

You can subscribe to the list, or change your existing subscription, in the sections below.

Hurd-devel Subscribers
(The subscribers list is only available to the list administrator.)

Enter your admin address and password to visit the subscribers list:

Admin address: Password:   

To unsubscribe from Hurd-devel, get a password reminder, or change your subscription options enter your subscription email address:

If you leave the field blank, you will be prompted for your email address


Hurd-devel list run by tschwinge at gnu.org
Hurd-devel administrative interface (requires authorization)
Overview of all gnu.org mailing lists

Delivered by Mailman
version 2.1.21
Python Powered GNU's Not Unix