mailinglists

早期freebsd实现

This list/newsgroup will be for the posting, by their authors, of lisp
and C sources and patches that improve GNU Emacs.  Its contents will
be reviewed by FSF for inclusion in future releases of GNU Emacs.

Please do NOT discuss or request source code here.  Use
help-gnu-emacs/gnu.emacs.help for those purposes.  This allows the
automatic archiving of sources posted to this list/newsgroup.

Please do NOT post such sources to any other GNU mailing list (e.g
help-gnu-emacs) or gnUSENET newsgroups (e.g. gnu.emacs.help).  It's up
to each poster to decide whether to cross-post to any non-gnUSENET
newsgroup (e.g. comp.emacs or vmsnet.sources).

Please do NOT announce that you have posted source code to
gnu.emacs.sources to any other GNU mailing list (e.g. help-gnu-emacs) or
gnUSENET newsgroups (e.g. gnu.emacs.help).  People who want to keep up
with sources will read this list/newsgroup.  It's up to each poster to
decide whether to announce a gnu.emacs.sources article in any
non-gnUSENET newsgroup (e.g comp.emacs or comp.sources.d).

If source or patches that were previously posted or a simple fix is
requested in help-gnu-emacs, please mail it to the requester.  Do NOT
repost it.  If you also want something that is requested, send mail to
the requester asking him to forward it to you.  This kind of traffic is
best handled by e-mail, not by a broadcast medium that reaches thousands
of sites.

If the source is very long (>10k bytes) send mail offering to send it.
This prevents the requester from getting many redundant copies and saves
network bandwidth.

* [e-mail] to subscribe to help-gnu-emacs
** gnUSENET newsgroup: gnu.emacs.help	(and one-way into comp.emacs)
** Send contributions to: [e-mail]

This list is the place for users and installers of GNU Emacs to ask for
help.  Please send bug reports to bug-gnu-emacs instead of posting them
here.

Since help-gnu-emacs a very large list, send it only those items that are
seriously important to many people.

If source or patches that were previously posted or a simple fix is
requested in help-gnu-emacs, please mail it to the requester.  Do NOT
repost it.  If you also want something that is requested, send mail to
the requester asking him to forward it to you.  This kind of traffic is
best handled by e-mail, not a broadcast medium that reaches thousands of
sites.

This list is also gated one way to USENET's newsgroup comp.emacs (once
known as net.emacs).  This one-way gating is done for users whose sites
get comp.emacs, but not gnu.emacs.help.  Users at non-USENET sites may
receive all articles from comp.emacs by making their request to:
[e-mail]

If Emacs crashes, or if you build Emacs following the standard procedure
on a system which Emacs is supposed to work on (see etc/MACHINES) and it
does not work at all, or if an editing command does not behave as it is
documented to behave, this is a bug.  Don't send bug reports to
help-gnu-emacs (gnu.emacs.help) or post them to comp.emacs; mail them to
bug-gnu-emacs instead.

See section '* General Information about help-* lists'.

* [e-mail] to subscribe to info-gnu-emacs
** gnUSENET newsgroup: gnu.emacs.announce	(and one-way into comp.emacs)
** Send announcements to: [e-mail]

This list distributes announcements and progress reports on GNU Emacs.
It is NOT for general discussion; please use help-gnu-emacs for that.

The list is filtered to remove items meant for info-gnu-emacs-request,
that can be answered by the moderator without bothering the list, or
should have been sent to another list.

info-gnu-emacs is also gated one way to USENET's newsgroup comp.emacs
(once known as net.emacs).  This one-way gating is done for users whose
sites get comp.emacs, but not gnu.emacs.announce.  Users at non-USENET
sites may receive all articles from comp.emacs by making their request
to: [e-mail]

Do not report GNU Emacs bugs to info-gnu-emacs or comp.emacs, instead
mail them to [e-mail].

See section '* General Information about info-* lists'.

* [e-mail] to subscribe to vms-gnu-emacs
** gnUSENET newsgroup: gnu.emacs.vms
** Send contributions to: [e-mail]
*** UUCP: ..!uunet!harvard!vms-gnu-emacs-request

This list was a working group who did the initial port of GNU Emacs to
the VMS operating system.  It still discusses problems and solutions to
the VMS port and the distribution of it.

* [e-mail] to subscribe to bug-bash
** gnUSENET newsgroup: gnu.bash.bug
** BASH bug reports to: [e-mail]

This list distributes, to the active maintainers of BASH (the Bourne
Again SHell), bug reports and fixes for, and suggestions for
improvements in BASH.  It is the place to report BASH bugs by all users
of BASH.

Always report the version number of the operating system, hardware, and
bash (flag -version on startup or check the variable $BASH_VERSION in a
running bash).

There are no other GNU mailing lists or gnUSENET newsgroups for BASH.

See section '* General Information about bug-* lists and reporting
program bugs'.

* [e-mail] to subscribe to bug-gdb
** gnUSENET newsgroup: gnu.gdb.bug
** GDB bug reports to: [e-mail]

This list distributes, to the active maintainers of GDB (Gnu's
DeBugger), bug reports and fixes for, and suggestions for improvements
in GDB.  It is the place to report GDB bugs by all users of GDB.

There are no other GNU mailing lists or gnUSENET newsgroups for GDB.

See section '* General Information about bug-* lists and reporting
program bugs'.

* [e-mail] to subscribe to bug-gcc
** gnUSENET newsgroup: gnu.gcc.bug
** GCC bug reports to: [e-mail]

This list distributes bug reports for, fixes for bugs in, and
suggestions for improvements in the GNU C Compiler to its active
developers.  It is the place to report GCC bugs by all testers of GCC.
The GNU C Compiler still has bugs in it, and is not quite ready for
everyday use.

Please don't send in a patch without a test case to illustrate the
problem the patch is supposed to fix.  Sometimes the patches aren't
correct or aren't the best way to do the job, and without a test case
there is no way to debug an alternate fix.

The most convenient form of test case is a piece of cpp output that can
be passed directly to cc1.  Preferably written in C, not C++.

Subscribers to bug-gcc automatically receive all info-gcc messages.

See section '* General Information about bug-* lists and reporting
program bugs'.

* [e-mail] to subscribe to help-gcc
** gnUSENET newsgroup: gnu.gcc.help
** Send contributions to: [e-mail]

This list is the place for users and installers of the GNU C Compiler to
ask for help.

If gcc crashes, or if you build gcc following the standard procedure on
a system which gcc is supposed to work on (see config.gcc) and it does
not work at all, or if an command line option does not behave as it is
documented to behave, this is a bug.  Don't send bug reports to help-gcc
(gnu.gcc.help); mail them to bug-gcc instead.

See section '* General Information about help-* lists'.

* [e-mail] to subscribe to info-gcc
** gnUSENET newsgroup: gnu.gcc.announce
** Send announcements to: [e-mail]

This list distributes announcements and progress reports on the GNU C
Compiler.  It is NOT for general discussion; please use help-gcc for
that.

The list is filtered to remove items meant for info-gcc-request, that
can be answered by the moderator without bothering the list, or should
have been sent to another list.

See section '* General Information about info-* lists'.

* [e-mail] to subscribe to bug-g++
** gnUSENET newsgroup: gnu.g++.bug
** G++ bug reports to: [e-mail]

This list distributes bug reports for, fixes for bugs in, and
suggestions for improvements in the GNU C++ Compiler to its active
developers.  It is the place to report G++ bugs by all testers of G++.

G++ uses the GNU C-Compiler back end.  Active developers may wish to
subscribe to [e-mail] as well.

Subscribers to bug-g++ automatically receive all info-g++ messages.

See section '* General Information about bug-* lists and reporting
program bugs'.

* [e-mail] to subscribe to help-g++
** gnUSENET newsgroup: gnu.g++.help	(and one-way into comp.lang.c++)
** Send contributions to: [e-mail]

This list is the place for users and installers of the GNU C++ Compiler
to ask for help.  Please send bug reports to bug-g++ instead of posting
them here.

help-g++ is also gated one way to USENET's newsgroup comp.lang.c++.
This one-way gating is done for users whose sites get comp.lang.c++, but
not gnu.g++.help.

If g++ crashes, or if you build g++ following the standard procedure on
a system which g++ is supposed to work on (see config.g++) and it does
not work at all, or if an command line option does not behave as it is
documented to behave, this is a bug.  Don't send bug reports to help-g++
(gnu.g++.help) or post them to comp.lang.c++; mail them to bug-g++
instead.

See section '* General Information about help-* lists'.

* [e-mail] to subscribe to info-g++
** gnUSENET newsgroup: gnu.g++.announce	(and one-way into comp.lang.c++)
** Send announcements to: [e-mail]

This list distributes announcements and progress reports on the GNU C++
Compiler.  It is NOT for general discussion; please use help-g++ for
that.

The list is filtered to remove items meant for info-g++-request, that
can be answered by the moderator without bothering the list, or should
have been sent to another list.

It is also gated one way to USENET's newsgroup comp.lang.c++.  This
one-way gating is done for users whose sites get comp.lang.c++, but not
gnu.g++.announce.

Do not report g++ bugs to info-g++ or comp.lang.c++, mail them to
[e-mail] instead.

See section '* General Information about info-* lists'.

* [e-mail] to subscribe to bug-lib-g++
** gnUSENET newsgroup: gnu.g++.lib.bug
** lib-g++ bug reports to: [e-mail]

This list distributes, to the active maintainers of lib-g++ (GNU's
library for C++), bug reports and fixes for, and suggestions for
improvements in lib-g++.  It is the place to report lib-g++ bugs by all