Follow @Openwall on Twitter for new release announcements and other news
[next>] [day] [month] [year] [list]
Message-ID: <87r1zh403l.fsf@oldenburg2.str.redhat.com>
Date: Thu, 30 Jan 2020 13:09:34 +0100
From: Florian Weimer <fweimer@...hat.com>
To: libc-coord@...ts.openwall.com
Subject: Welcome to the libc-coord list

Welcome to the libc-coord list!

This list is intended to coordinate work on run-time libraries for the C
programming language and its extensions.  Expected topics include:

- Proposals for portable library extensions
- Discussion and clarification of the behavior of already established
  interfaces
- Public review of proposals for the C standard or POSIX
- ABI-level changes that impact C implementations
- Coordination of the design and implementation of interfaces between
  compilers and libraries
- Other toolchain integration topics, such as debugger performance tools
  support

Posts to the list should be self-contained and include the material
relevant to the discussion, rather than relying solely on external
references.  Posting links to relevant external resources as well is
acceptable, but posting only links is discouraged.  Your message
should remain valuable even with all of the external resources gone.

Please be respectful of other people's work.  There is value in having
different implementations exploring various design choices.  But there
is also value in providing source code portability to programmers.
This list aims to help balancing these two goals.

To subscribe to the list, send mail to:

  <libc-coord-subscribe at lists.openwall.com>

The list posting address is:

  <libc-coord at lists.openwall.com>

You can also manage your subscription at <https://www.openwall.com/lists/>.

This list is lightly moderated (to deal with automated email
submissions), with Rich Felker and Florian Weimer as the initial
moderators, and the expectation that regular posters will be
white-listed.

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.