GNU Project Electronic Mailing Lists and gnUSENET Newsgroups Last Updated 1999-05-06 Please report improvements to: gnu@gnu.org* Mailing list archivesThe GNU mailing lists are archived atftp://ftp-mailing-list-archives.gnu.org/* GNU mailing lists are also distributed as USENET news groupsThe mailing lists are gated both ways with the gnu.all newsgroups atuunet. The one-to-one correspondence is indicated below. Ifyou don't know if your site is on USENET, ask your system administrator.If you are a USENET site and don't get the gnu.all newsgroups, pleaseask your USENET administrator to get them. If he has your feeds asktheir feeds, you should win. And everyone else wins: newsgroups makebetter use of the limited bandwidth of the computer networks and yourhome machine than mailing list traffic; and staying off the mailinglists make better use of the people who maintain the lists and themachines that the GNU people working with rms use (i.e. we have moretime to produce code!!). Thanx.* Getting the mailing lists directlyIf several users at your site or local network want to read a list andyou aren't a USENET site, Project GNU would prefer that you would set upone address that redistributes locally. This reduces overhead on ourpeople and machines, your gateway machine, and the network(s) used totransport the mail from us to you.* How to subscribe to and report bugs in mailing listsSend requests to be added or removed, to help-gnu-emacs-request (orinfo-gnu-request, bug-gdb-request, etc.), NOT to info-gnu-emacs (orinfo-gnu, etc.). Most <LIST_NAME>-request addresses are now handledautomagically by the SmartList program.If you need to report problems to a human, send mail to gnu@gnu.orgexplaining the problem.Many of the GNU mailing lists are very large and are received by manypeople. Please don't send them anything that is not seriously importantto all their readers. All GNU mailing lists are unmoderated mailreflectors, except info-gnu, info-gnu-emacs, info-gcc, info-g++,info-gnu-fortran.All addresses below are in internet format. Consult the mail guru foryour computer to figure out address syntaxes from other networks. FromUUCP machines: ..!ucbvax!gnu.org!ADDRESS ..!uunet!gnu.org!ADDRESSIf a message you mail to a list is returned from a MAILER-DAEMON (oftenwith the line: ----- Transcript of session follows ----- don't resend the message to the list. All this return means is thatyour original message failed to reach a few addresses on the list. Suchmessages are NEVER a reason to resend a piece of mail a 2nd time. Thisjust bothers all (less the few delivery failures (which will probablyjust fail again!)) of the readers of the list with a message they havealready seen. It also wastes computer and network resources.It is appropriate to send these to the -request address for a list, andask them to check the problem out.* Send Specific Requests for Information to: gnu@gnu.orgSpecific requests for information about obtaining GNU software, or GNUactivities in Cambridge and elsewhere can be directed to: gnu@gnu.org* General Information about all listsPlease keep each message under 25,000 characters. Some mailers bouncemessages that are longer than this. If your message is long, it isgenerally better to send a message offering to make the large fileavailable to only those people who want it (e.g. mailing it to peoplewho ask, or putting it up for FTP). In the case of gnu.emacs.sources,somewhat larger postings (up to 10 parts of no more than 25,000characters each) are acceptable (assuming they are likely to be ofinterest to a reasonable number of people); if it is larger than thathave it added to archive.cis.ohio-state.edu (the GNU Emacs Lisp ftp anduucp archive) and announce its location there. Good bug reports areshort. See section '* General Information about bug-* lists and ...'for further details.Most of the time, when you reply to a message sent to a list, the replyshould not go to the list. But most mail reading programs supply, bydefault, all the recipients of the original as recipients of the reply.Make a point of deleting the list address from the header when it doesnot belong. This prevents bothering all readers of a list, and reducesnetwork congestion.The GNU mailing lists and newsgroups, like the GNU project itself, existto promote the freedom to share software. So don't use these lists topromote or recommend non-free software or documentation, likeproprietary books on GNU software. (Using them to post orderinginformation is the ultimate faux pas.) If there is no free program todo a certain task, then somebody should write one! Similarly, freedocumentation that is inadequate should be improved--a way in whichnon-programmers can make a valuable contribution. See also the articleat <URL:http://www.gnu.org/philosophy/free-doc.html>.* General Information about info-* listsThese lists and their newsgroups are meant for important announcements.Since the GNU project uses software development as a means for socialchange, the announcements may be technical or political.Most GNU projects info-* lists (and their corresponding gnu.*.announcenewsgroups) are moderated to keep their content significant andrelevant. If you have a bug to report, send it to the bug-* list. Ifyou need help on something else and the help-* list exists, ask it.See section '* General Information about all lists'.* General Information about help-* listsThese lists (and their newsgroups) exist for anyone to ask questionsabout the GNU software that the list deals with. The lists are read bypeople who are willing to take the time to help other users.When you answer the questions that people ask on the help-* lists, keepin mind that you shouldn't answer by promoting a proprietary program asa solution. The only real solutions are the ones all the readers canshare.If a program crashes, or if you build it following the standardprocedure on a system on which it is supposed to work and it does notwork at all, or if an command does not behave as it is documented tobehave, this is a bug. Don't send bug reports to a help-* list; mailthem to the bug-* list instead.See section '* General Information about all lists'.* General Information about bug-* lists and reporting program bugsIf you think something is a bug in a program, it might be one; or, itmight be a misunderstanding or even a feature. Before beginning toreport bugs, please read the section ``Reporting Emacs Bugs'' toward theend of the GNU Emacs reference manual (or node Emacs/Bugs in Emacs'sbuilt-in Info system) for a discussion of how and when to send in bugreports. For GNU programs other than GNU Emacs, also consult theirdocumentation for their bug reporting procedures. Always include theversion number of the GNU program, as well as the operating system andmachine the program was ran on (if the program doesn't have a versionnumber, send the date of the latest entry in the file ChangeLog). ForGNU Emacs bugs, type "M-x emacs-version". A debugger backtrace of anycore dump can also be useful. Be careful to separate out hypothesisfrom fact! For bugs in GNU Emacs lisp, set variable debug-on-error tot, and re-enter the command(s) that cause the error message; Emacs willpop up a debug buffer if something is wrong; please include a copy ofthe buffer in your bug report. Please also try to make your bug reportas short as possible; distill the problem to as few lines of code and/orinput as possible. GNU maintainers give priority to the shortest, highquality bug reports.Please don't send in a patch without a test case to illustrate theproblem the patch is supposed to fix. Sometimes the patches aren'tcorrect or aren't the best way to do the job, and without a test casethere is no way to debug an alternate fix.The purpose of reporting a bug is to enable the bug to be fixed for thesake of the whole community of users. You may or may not receive aresponse; the maintainers will send one if that helps them find orverify a fix. Most GNU maintainers are volunteers and all areoverworked; they don't have time to help individuals and still fix thebugs and make the improvements that everyone wants. If you want helpfor yourself in particular, you may have to hire someone. The GNUproject maintains a list of people providing such services. It isdistributed with GNU Emacs in file etc/SERVICE, and can be requestedfrom gnu@gnu.org.Anything addressed to the implementors and maintainers of a GNU programvia a bug-* list, should NOT be sent to the corresponding info-* orhelp-* list.Please DON'T post your bug reports on the gnu.*.bug newsgroups! Mailthem to bug-*@gnu.org instead! At first sight, it seems to make nodifference: anything sent to one will be propagated to the other; but: - if you post on the newsgroup, the information about how toreach you is lost in the message that goes on the mailing list. Itcan be very important to know how to reach you, if there is anythingin the bug report that we don't understand; - bug reports reach the GNU maintainers quickest when they aresent to the bug-* mailing list submittal address; - mail is much more reliable then netnews; and - if the internet mailers can't get your bug report delivered,they almost always send you an error message, so you can find anotherway to get the bug report in. When netnews fails to get your messagedelivered to the maintainers, you'll never know about it and themaintainers will never see the bug report.And please DON'T post your GNU bug reports to comp.* or other gnu.*newsgroups, they never make it to the GNU maintainers at all. Pleasemail them to bug-*@gnu.org instead!See section '* General Information about all lists'.* info-gnu-request@gnu.org to subscribe to info-gnu** gnUSENET newsgroup: gnu.announce** Send announcements to: info-gnu@gnu.orgThis list distributes progress reports on the GNU Project. It is alsoused by the GNU Project to ask people for various kinds of help. It isNOT for general discussion.The list is filtered to remove items meant for info-gnu-request, thatcan be answered by the moderator without bothering the list, or shouldhave been sent to another list.See section '* General Information about info-* lists'.* gnu-misc-discuss-request@gnu.org to subscribe to gnu-misc-discuss** gnUSENET newsgroup: gnu.misc.discuss** Send contributions to: gnu-misc-discuss@gnu.orgThis list is for serious discussion of freed software, the GNU Project,the GNU Manifesto, and their implications. It's THE place fordiscussion that is not appropriate in the other GNU mailing lists andgnUSENET newsgroups.Flaming is out of place. Tit-for-tat is not welcome. Repetitionshould not occur.Good READING and writing are expected. Before posting, wait a while,cool off, and think.Don't use this group for complaints and bug reports about GNU software!The maintainers don't read this group; they won't see your complaint.Use the appropriate bug-reporting mailing list instead, so that peoplewho can do something about the problem will see it.Don't trust pronouncements made on gnu-misc-discuss about what GNU is,what FSF position is, what the GNU General Public License is, etc.,unless they are made by someone you know is well connected with GNU andare sure the message is not forged.USENET and gnUSENET readers are expected to have read ALL the articlesin news.announce.newusers before posting. If news.announce.newusers isempty at your site, wait (the articles are posted monthly), your postingisn't that urgent! Readers on the Internet can anonymous FTP thesearticles from host ftp.uu.net under directory ??Someone from the Free Software Foundation will attempt to follow thisgroup as time and volume permits.Remember, "GNUs Not Unix" and "gnUSENET is Not USENET". We havehigher standards!Note that sending technical questions about specific GNU software tognu-misc-discuss is likely to be less useful than sending them to theappropriate mailing list or gnUSENET newsgroup, since more technicalpeople read those.* bug-gnu-sql-request@gnu.org to subscribe to bug-gnu-sql** gnUSENET newsgroup: NONE PLANNED** GNU-SQL BUG reports to: bug-gnu-sql@gnu.orgThis list distributes, to the active maintainers of GNU's SQL (GNU's SQLfull scale database server), bug reports and fixes for, and suggestionsfor improvements to GNU's SQL. User discussion of GNU's SQL also occurshere.There are no other GNU mailing lists or gnUSENET newsgroups for GNU's SQL.See section '* General Information about bug-* lists and reportingprogram bugs'.* bug-guile-request@gnu.org to subscribe to bug-guile** gnUSENET newsgroup: NONE PLANNED** GUILE BUG reports to: bug-guile@gnu.orgThis list distributes, to the active maintainers of GUILE (GNU'sUbiquitous Extension Language), bug reports and fixes for, and suggestions forimprovements to GUILE. User discussion of GUILE also occurs here.There are no other GNU mailing lists or gnUSENET newsgroups for GUILE .See section '* General Information about bug-* lists and reportingprogram bugs'.* guile-sources-request@gnu.org to subscribe to guile-sources** gnUSENET newsgroup: NONE PLANNED** Guile source code to: guile-sources@gnu.orgThis list will be for the posting, by their authors, of GUILE, Scheme,and C sources and patches that improve Guile. Its contents will bereviewed by the FSF for inclusion in future releases of GUILE.Please do NOT discuss or request source code here. Use bug-guile forthose purposes. This allows the automatic archiving of sources postedto this list.Please do NOT post such sources to any other GNU mailing list (e.gbug-guile) or gnUSENET newsgroups. It's up to each poster to decidewhether to cross-post to any non-gnUSENET newsgroup.Please do NOT announce that you have posted source code to guile.sourcesto any other GNU mailing list (e.g. bug-guile) or gnUSENET newsgroups.People who want to keep up with sources will read this list. It's up toeach poster to decide whether to announce a guile.sources article in anynon-gnUSENET newsgroup (e.g. comp.emacs or comp.sources.d).If source or patches that were previously posted or a simple fix isrequested in bug-guile, please mail it to the requester. Do NOTrepost it. If you also want something that is requested, send mail tothe requester asking him to forward it to you. This kind of traffic isbest handled by e-mail, not by a broadcast medium that reaches millionsof sites.If the requested source is very long (>10k bytes) send mail offering tosend it. This prevents the requester from getting many redundant copiesand saves network bandwidth.* bug-gnustep-request@gnu.org to subscribe to bug-gnustep** gnUSENET newsgroup: gnu.gnustep.bug** Gnustep bug reports to: bug-gnustep@gnu.org** FAQ-URL: none known** FAQ-Archive-name: none known** FAQ-Posting-frequency: none knownThis list distributes bug reports for, fixes for bugs in, andsuggestions for improvements in GNUstep to its active developers.Subscribers to bug-gnustep get all info-gnustep messages.See section '* General Information about bug-* lists and reportingprogram bugs'.* help-gnustep-request@gnu.org to subscribe to help-gnustep** gnUSENET newsgroup: gnu.gnustep.help** Send contributions to: help-gnustep@gnu.org** FAQ-URL: none known** FAQ-Archive-name: none known** FAQ-Posting-frequency: none knownThis list is the place for users and installers of the GNUstep to askfor help. Please send bug reports to bug-gnustep@gnu.orginstead of posting them here.See section '* General Information about help-* lists'.* discuss-gnustep-request@gnu.org to subscribe to discuss-gnustep** gnUSENET newsgroup: gnu.gnustep.discuss** Send contributions to: discuss-gnustep@gnu.org** FAQ-URL: none known** FAQ-Archive-name: none known** FAQ-Posting-frequency: none knownThis list is the place for GNUstep users and developers to discussGNUstep. Please send bug reports to bug-gnustep@gnu.orginstead of posting them here.See section '* General Information about discuss-* lists'.* info-gnustep-request@gnu.org to subscribe to info-gnustep** gnUSENET newsgroup: gnu.gnustep.announce** Send announcements to: info-gnustep@gnu.org** FAQ-URL: none known** FAQ-Archive-name: none known** FAQ-Posting-frequency: none knownThis list distributes announcements and progress reports on GNUstep.It is NOT for general discussion; please use discuss-gnustep for that.The list is filtered to remove items meant for info-gnustep-request, thatcan be answered by the moderator without bothering the list, or shouldhave been sent to another list.Do not report GNUstep bugs to info-gnustep, help-gnustep, ordiscuss-gnustep, mail them to bug-gnustep@gnu.org instead.See section '* General Information about info-* lists'.* bug-hurd-request@gnu.org to subscribe to bug-hurd** gnUSENET newsgroup: NONE** Hurd bug reports to: bug-hurd@gnu.orgThis list distributes bug reports for, fixes for bugs in, andsuggestions for improvements in the GNU Hurd to its active developers.No info-gnu-hurd list is planned. Announcements about the GNU Hurd willbe made to the list info-gnu@gnu.org (see above).See section '* General Information about bug-* lists and reportingprogram bugs'.* help-hurd-request@gnu.org to subscribe to help-hurd** gnUSENET newsgroup: NONE** Send contributions to: help-hurd@gnu.orgThis list is the place for users and installers of the GNU Hurd to askfor help.No info-gnu-hurd list is planned. Announcements about the GNU Hurd willbe made to the list info-gnu@gnu.org (see above).See section '* General Information about help-* lists'.* hurd-ann-request@gnu.org IS NOW DEFUNCT** gnUSENET newsgroup: NEVER EXISTED** DEAD address: hurd-ann@gnu.orgThis list is dead. Announcements about the GNU Hurd will be made to thelist info-gnu@gnu.org (see above).* discuss-gnu-electric-request@gnu.org to subscribe to discuss-gnu-electric** gnUSENET newsgroup: NONE** Send contributions to: discuss-gnu-electric@gnu.orgThis list is the place for user discussion of Gnu Electric, asophisticated electrical CAD system that can handle many forms ofcircuit design. Please send bug reports to bug-gnu-electric@gnu.org(see next entry).* bug-gnu-electric-request@gnu.org to subscribe to bug-gnu-electric** gnUSENET newsgroup: NONE** Gnu Electric bug reports to: bug-gnu-electric@gnu.orgThis list distributes, to the active maintainers of GNU Electric, bugreports and fixes for, and suggestions for improvements in GNU Electric,a sophisticated electrical CAD system that can handle many forms ofcircuit design.No info-gnu-electric list exists; announcements of new releases aremade to info-gnu@gnu.org (see above).See section '* General Information about bug-* lists and reportingprogram bugs'.* bug-gnu-emacs-request@gnu.org to subscribe to bug-gnu-emacs** gnUSENET newsgroup: gnu.emacs.bug** Gnu Emacs bug reports to: bug-gnu-emacs@gnu.orgThis list distributes, to the active maintainers of GNU Emacs, bugreports and fixes for, and suggestions for improvements in GNU Emacs.Send bugs in the GNU Emacs Lisp reference manual to: lisp-manual-bugs@gnu.orglisp-manual-bugs is neither a mailing list nor a gnUSENET newsgroup.It's just a bug-reporting address.Subscribers to bug-gnu-emacs get all info-gnu-emacs messages.See section '* General Information about bug-* lists and reportingprogram bugs'.* gnu-emacs-sources-request@gnu.org to subscribe to gnu-emacs-sources** gnUSENET newsgroup: gnu.emacs.sources** Gnu Emacs source code to: gnu-emacs-sources@gnu.orgThis list/newsgroup will be for the posting, by their authors, of EmacsLisp and C sources and patches that improve GNU Emacs. Its contentswill be reviewed by the FSF for inclusion in future releases of GNUEmacs.Please do NOT discuss or request source code here. Usehelp-gnu-emacs/gnu.emacs.help for those purposes. This allows theautomatic archiving of sources posted to this list/newsgroup.Please do NOT post such sources to any other GNU mailing list (e.ghelp-gnu-emacs) or gnUSENET newsgroups (e.g. gnu.emacs.help). It's upto each poster to decide whether to cross-post to any non-gnUSENETnewsgroup (e.g. comp.emacs or vmsnet.sources).Please do NOT announce that you have posted source code tognu.emacs.sources to any other GNU mailing list (e.g. help-gnu-emacs) orgnUSENET newsgroups (e.g. gnu.emacs.help). People who want to keep upwith sources will read this list/newsgroup. It's up to each poster todecide whether to announce a gnu.emacs.sources article in anynon-gnUSENET newsgroup (e.g. comp.emacs or comp.sources.d).If source or patches that were previously posted or a simple fix isrequested in help-gnu-emacs, please mail it to the requester. Do NOTrepost it. If you also want something that is requested, send mail tothe requester asking him to forward it to you. This kind of traffic isbest handled by e-mail, not by a broadcast medium that reaches millionsof sites.If the requested source is very long (>10k bytes) send mail offering tosend it. This prevents the requester from getting many redundant copiesand saves network bandwidth.* help-gnu-emacs-request@gnu.org to subscribe to help-gnu-emacs** gnUSENET newsgroup: gnu.emacs.help (and one-way into comp.emacs)** Send contributions to: help-gnu-emacs@gnu.orgThis list is the place for users and installers of GNU Emacs to ask forhelp. Please send bug reports to bug-gnu-emacs instead of posting themhere.Since help-gnu-emacs is a very large list, send it only those items thatare seriously important to many people.If source or patches that were previously posted or a simple fix isrequested in help-gnu-emacs, please mail it to the requester. Do NOTrepost it. If you also want something that is requested, send mail tothe requester asking him to forward it to you. This kind of traffic isbest handled by e-mail, not a broadcast medium that reaches millions ofsites.This list is also gated one way to USENET's newsgroup comp.emacs (onceknown as net.emacs). This one-way gating is done for users whose sitesget comp.emacs, but not gnu.emacs.help. Users at non-USENET sites mayreceive all articles from comp.emacs by making their request to:unix-emacs-request@bbn.comIf Emacs crashes, or if you build Emacs following the standard procedureon a system which Emacs is supposed to work on (see etc/MACHINES) and itdoes not work at all, or if an editing command does not behave as it isdocumented to behave, this is a bug. Don't send bug reports tohelp-gnu-emacs (gnu.emacs.help) or post them to comp.emacs; mail them tobug-gnu-emacs@gnu.org instead.See section '* General Information about help-* lists'.* info-gnu-emacs-request@gnu.org to subscribe to info-gnu-emacs** gnUSENET newsgroup: gnu.emacs.announce (and one-way into comp.emacs)** Send announcements to: info-gnu-emacs@gnu.orgThis 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, orshould 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 whosesites get comp.emacs, but not gnu.emacs.announce. Users at non-USENETsites may receive all articles from comp.emacs by making their requestto: unix-emacs-request@bbn.comDo not report GNU Emacs bugs to info-gnu-emacs or comp.emacs, insteadmail them to bug-gnu-emacs@gnu.org.See section '* General Information about info-* lists'.* vms-gnu-emacs-request@gnu.org to subscribe** gnUSENET newsgroup: gnu.emacs.vms** Send contributions to: vms-gnu-emacs@gnu.orgThis list was a working group who did the initial port of GNU Emacs tothe VMS operating system. It still discusses problems and solutions tothe VMS port and the distribution of it.* bug-bash-request@gnu.org to subscribe to bug-bash** gnUSENET newsgroup: gnu.bash.bug** BASH bug reports to: bug-bash@gnu.orgThis list distributes, to the active maintainers of BASH (the BourneAgain SHell), bug reports and fixes for, and suggestions forimprovements in BASH. User discussion of BASH also occurs here.Always report the version number of the operating system, hardware, andbash (flag -version on startup or check the variable $BASH_VERSION in arunning bash).There are no other GNU mailing lists or gnUSENET newsgroups for BASH.See section '* General Information about bug-* lists and reportingprogram bugs'.* bug-gdb-request@gnu.org to subscribe to bug-gdb** gnUSENET newsgroup: gnu.gdb.bug** GDB bug reports to: bug-gdb@gnu.orgThis list distributes, to the active maintainers of GDB (Gnu'sDeBugger), bug reports and fixes for, and suggestions for improvementsin GDB. This list is also for user discussion.There are no other GNU mailing lists or gnUSENET newsgroups for GDB.See section '* General Information about bug-* lists and reportingprogram bugs'.* bug-ncurses-request@gnu.org to subscribe to bug-ncurses** gnUSENET newsgroup: none** NCURSES bug reports to: bug-ncurses@gnu.orgThis list distributes, to the active maintainers of ncurses(a free implementation of the Unix curses API) bug reports and fixesfor, and suggestions for improvements in ncurses. Users can alsosubscribe to this list.See section '* General Information about bug-* lists and reportingprogram bugs'.* help-ncurses-request@gnu.org to subscribe to help-ncurses** gnUSENET newsgroup: none** posts go to: help-ncurses@gnu.orgThis list is the place for users and installers of ncurses to ask forhelp. Please send bug reports to bug-ncurses instead of posting themhere.See section '* General Information about help-* lists'* bug-gnats-request@gnu.org to subscribe to bug-gnats** gnUSENET newsgroup: None** GNATS bug reports to: bug-gnats@gnu.orgThis list distributes, to the active maintainers of GNATS (GNats: ATracking System), bug reports and fixes for, and suggestions for improvementsin GNATS. This list is also for user discussion.There are no other GNU mailing lists or gnUSENET newsgroups for GNATS.See section '* General Information about bug-* lists and reportingprogram bugs'.* bug-octave-request@bevo.che.utexas.edu to subscribe to bug-octave** gnUSENET newsgroup: NONE PLANNED** Octave bug reports to: bug-octave@bevo.che.utexas.eduThis list distributes, to the active maintainers of Octave (a systemfor numerical computations), bug reports and fixes for, andsuggestions for improvements to Octave.The help-octave mailing list is for user discussion of Octave.See section '* General Information about bug-* lists and reportingprogram bugs'.* help-octave-request@bevo.che.utexas.edu to subscribe to help-octave** gnUSENET newsgroup: NONE PLANNED** Send contributions to: help-octave@bevo.che.utexas.eduThis list is the place for users and installers of Octave to ask forhelp. Please send bug reports to bug-octave instead of posting themhere.If Octave crashes, or if you build Octave following the standardprocedure on a system on which Octave is supposed to work on and itdoes not work at all, or if a command does not behave as it isdocumented to behave, this is a bug. Don't send bug reports tohelp-octave; mail them to bug-octave@che.utexas.edu instead.See section '* General Information about help-* lists'.* bug-bison-request@gnu.org to subscribe to bug-bison** gnUSENET newsgroup: NONE** Bison bug reports to: bug-bison@gnu.orgThis list distributes, to the active maintainers of Bisonbug reports and fixes for, and suggestions for improvementsin Bison. User discussion of Bison bugs occurs here.See section '* General Information about bug-* lists and reportingprogram bugs'.* help-bison-request@gnu.org to subscribe to help-bison** gnUSENET newsgroup: NONE** Send contributions to: help-bison@gnu.orgThis list is the place for users and installers of Bisonto ask for help. Please send bug reports to bug-bison insteadof posting them here.See section '* General Information about help-* lists'.* bug-make-request@gnu.org to subscribe to bug-make** gnUSENET newsgroup: NONE** Make bug reports to: bug-make@gnu.orgThis list distributes, to the active maintainers of GNU makebug reports and fixes for, and suggestions for improvementsin GNU make. User discussion of GNU make bugs occurs here.See section '* General Information about bug-* lists and reportingprogram bugs'.* help-make-request@gnu.org to subscribe to help-make** gnUSENET newsgroup: NONE** Send contributions to: help-make@gnu.orgThis list is the place for users and installers of GNU maketo ask for help. Please send bug reports to bug-make insteadof posting them here.See section '* General Information about help-* lists'.* help-flex-request@gnu.org to subscribe to help-flex** gnUSENET newsgroup: NONE** Send contributions to: help-flex@gnu.orgThis list is the place for users and installers of Flexto ask for help. Please send bug reports to bug-gnu-utils insteadof posting them here.See section '* General Information about help-* lists'.* bug-rcs-request@gnu.org to subscribe to bug-rcs** gnUSENET newsgroup: NONE** RCS bug reports to: bug-rcs@gnu.orgThis list distributes, to the active maintainers of RCSbug reports and fixes for, and suggestions for improvementsin RCS. User discussion of RCS bugs occurs here.See section '* General Information about bug-* lists and reportingprogram bugs'.* help-rcs-request@gnu.org to subscribe to help-rcs** gnUSENET newsgroup: NONE** Send contributions to: help-rcs@gnu.orgThis list is the place for users and installers of RCSto ask for help. Please send bug reports to bug-rcs insteadof posting them here.See section '* General Information about help-* lists'.* bug-gcc-request@gnu.org to subscribe to bug-gcc** gnUSENET newsgroup: gnu.gcc.bug** GCC bug reports to: bug-gcc@gnu.orgThis list distributes bug reports for, fixes for bugs in, andsuggestions for improvements in the GNU C Compiler to its activedevelopers.Please don't send in a patch without a test case to illustrate theproblem the patch is supposed to fix. Sometimes the patches aren'tcorrect or aren't the best way to do the job, and without a test casethere is no way to debug an alternate fix.The most convenient form of test case is a piece of cpp output that canbe passed directly to cc1. Preferably written in C, not C++ orObjective C.Subscribers to bug-gcc get all info-gcc messages.See section '* General Information about bug-* lists and reportingprogram bugs'.* help-gcc-request@gnu.org to subscribe to help-gcc** gnUSENET newsgroup: gnu.gcc.help** Send contributions to: help-gcc@gnu.orgThis list is the place for users and installers of the GNU C Compiler toask for help.If gcc crashes, or if you build gcc following the standard procedure ona system which gcc is supposed to work on (see config.sub) and it doesnot work at all, or if an command line option does not behave as it isdocumented to behave, this is a bug. Don't send bug reports to help-gcc(gnu.gcc.help); mail them to bug-gcc@gnu.org instead.See section '* General Information about help-* lists'.* info-gcc-request@gnu.org to subscribe to info-gcc** gnUSENET newsgroup: gnu.gcc.announce** Send announcements to: info-gcc@gnu.orgThis list distributes announcements and progress reports on the GNU CCompiler. It is NOT for general discussion; please use help-gcc forthat.The list is filtered to remove items meant for info-gcc-request, thatcan be answered by the moderator without bothering the list, or shouldhave been sent to another list.See section '* General Information about info-* lists'.* bug-gnu960-request@ichips.intel.com to subscribe to bug-gnu960** gnUSENET newsgroup: NONE PLANNED** Intel 960 Port bug reports to: bug-gnu960@ichips.intel.comThis list distributes bug reports for, fixes for bugs in, andsuggestions for improvements in Intel's port of GNU software to theIntel 960 microprocessor.You can also fax to: GNU/960 - 1-503-696-4930.There are no other GNU mailing lists or gnUSENET newsgroups for Intel'sport of GNU software to the Intel 960 microprocessor.See section '* General Information about bug-* lists and reportingprogram bugs'.* bug-glibc-request@gnu.org to subscribe to bug-glibc** gnUSENET newsgroup: gnu.glibc.bug** GNU C Library bug reports to: bug-glibc@gnu.orgThis list distributes, to the active maintainers of glibc (GNU's Clibrary), bug reports and fixes for, and suggestions for improvements inglibc. User discussion of glibc also occurs here.Announcements of new releases of glibc are made on both info-gcc andbug-glibc.There are no other GNU mailing lists or gnUSENET newsgroups for the GNUC Library.See section '* General Information about bug-* lists and reportingprogram bugs'.* bug-g++-request@gnu.org to subscribe to bug-g++** gnUSENET newsgroup: gnu.g++.bug** G++ bug reports to: bug-g++@gnu.orgThis list distributes bug reports for, fixes for bugs in, andsuggestions for improvements in the GNU C++ Compiler to its activedevelopers.G++ uses the GNU C-Compiler back end. Active developers may wish tosubscribe to bug-gcc@gnu.org as well.Subscribers to bug-g++ get all info-g++ messages.See section '* General Information about bug-* lists and reportingprogram bugs'.* help-g++-request@gnu.org to subscribe to help-g++** gnUSENET newsgroup: gnu.g++.help (and one-way into comp.lang.c++)** Send contributions to: help-g++@gnu.orgThis list is the place for users and installers of the GNU C++ Compilerto ask for help. Please send bug reports to bug-g++@gnu.orginstead 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++, butnot gnu.g++.help.See section '* General Information about help-* lists'.* info-g++-request@gnu.org to subscribe to info-g++** gnUSENET newsgroup: gnu.g++.announce (and one-way into comp.lang.c++)** Send announcements to: info-g++@gnu.orgThis list distributes announcements and progress reports on the GNU C++Compiler. It is NOT for general discussion; please use help-g++ forthat.The list is filtered to remove items meant for info-g++-request, thatcan be answered by the moderator without bothering the list, or shouldhave been sent to another list.It is also gated one way to USENET's newsgroup comp.lang.c++. Thisone-way gating is done for users whose sites get comp.lang.c++, but notgnu.g++.announce.Do not report g++ bugs to info-g++ or comp.lang.c++, mail them tobug-g++@gnu.org instead.See section '* General Information about info-* lists'.* bug-lib-g++-request@gnu.org to subscribe to bug-lib-g++** gnUSENET newsgroup: gnu.g++.lib.bug** lib-g++ bug reports to: bug-lib-g++@gnu.orgThis list distributes, to the active maintainers of libg++ (GNU'slibrary for C++), bug reports and fixes for, and suggestions forimprovements in lib-g++. User discussion of libg++ also occurs here.Announcements of new releases of libg++ are made on both info-g++ andbug-lib-g++.There are no other GNU mailing lists or gnUSENET newsgroups for GNU'sG++ Library.See section '* General Information about bug-* lists and reportingprogram bugs'.* info-gnu-fortran-request@gnu.org to subscribe to info-gnu-fortran** gnUSENET newsgroup: NONE YET** Send announcements to: info-gnu-fortran@gnu.orgThis list is for progress reports and release notices for G77/GNUFortran.The list is filtered to remove items meant for info-gnu-fortran-request,that can be answered by the moderator without bothering the list, or thatshould have been sent to another list.People on the Internet can get a current status report by fingering theaddress fortran@gnu.org or by looking at the GNU Fortran web pages athttp://www.gnu.org/software/fortran/fortran.html.Users looking for help should ask the help-gnu-fortran@gnu.org list.Bug reports should go to bug-gnu-fortran@gnu.org.See section '* General Information about info-* lists'.* help-gnu-fortran-request@gnu.org to subscribe to help-gnu-fortran** gnUSENET newsgroup: NONE YET** Send messages to: help-gnu-fortran@gnu.orgThis list is for user requests for help and discussion about GNUFortran (G77). Bug reports should go to bug-gnu-fortran@gnu.org.See section '* General Information about help-* lists'.* bug-gnu-fortran@@gnu.org to subscribe to bug-gnu-fortran** gnUSENET newsgroup: NONE YET** Send messages to: help-gnu-fortran@gnu.orgThis list is for bug-reports and patches for GNU Fortran(G77). Requests for help should go to help-gnu-fortran@gnu.org.See section '* General Information about bug-* lists and reportingprogram bugs'.* bug-oleo-request@gnu.org to subscribe to bug-oleo** gnUSENET newsgroup: NONE PLANNED** Oleo bug reports to: bug-oleo@gnu.orgThis list distributes, to the active maintainers of Oleo (the GNUspreadsheet), bug reports and fixes for, and suggestions forimprovements to Oleo. User discussion of Oleo also occurs here.There are no other GNU mailing lists or gnUSENET newsgroups for Oleo.See section '* General Information about bug-* lists and reportingprogram bugs'.* bug-gmp-request@gnu.org to subscribe to bug-gmp** gnUSENET newsgroup: NONE PLANNED** gmp bug reports to: bug-gmp@gnu.orgThis list distributes, to the active maintainers of gmp (the GNUMultiple Precision Library), bug reports and fixes for, and suggestionsfor improvements to gmp. User discussion of gmp also occurs here.There are no other GNU mailing lists or gnUSENET newsgroups for gmp .See section '* General Information about bug-* lists and reportingprogram bugs'.* bug-panorama-request@gnu.org to subscribe to bug-panorama** gnUSENET newsgroup: NONE PLANNED** panorama bug reports to: bug-panorama@gnu.orgThis list is a place for users of Panorama to send bug reports, fixesfor them, and suggestions for improvements.See section '* General Information about bug-* lists and reportingprogram bugs'.* help-panorama-request@gnu.org to subscribe to help-panorama** gnUSENET newsgroup: NONE PLANNED** articles to: help-panorama@gnu.orgThis list is the place for users and installers of Panorama to ask forhelp. Please send bug reports to bug-panorama instead of posting themhere.* devel-panorama-request@gnu.org to subscribe to devel-panorama** gnUSENET newsgroup: NONE PLANNED** articles to: devel-panorama@gnu.orgThis list is a place for discussion among active developers of PanoramaAPI or any of its plugins.* bug-mana-request@gnu.org to subscribe to bug-mana** gnUSENET newsgroup: NONE PLANNED** mana bug reports to: bug-mana@gnu.orgThis list distributes, to the active maintainers of mana (the GNUstand-alone mail reader), bug reports and fixes for, and suggestionsfor improvements to mana. User discussion of mana also occurs here.There are no other GNU mailing lists or gnUSENET newsgroups for mana.See section '* General Information about bug-* lists and reportingprogram bugs'.* bug-zebra-request@gnu.org to subscribe to bug-zebra** gnUSENET newsgroup: NONE PLANNED** zebra bug reports to: bug-zebra@gnu.orgThis list distributes, to the active maintainers of zebra (a GPLedprogram to manage TCP/IP based routing protocols), bug reports, bug fixes,and suggestions for improvements to zebra. User discussion of zebraalso occurs here.There are no other GNU mailing lists or gnUSENET newsgroups for zebra.See section '* General Information about bug-* lists and reportingprogram bugs'.* bug-cfengine-request@gnu.org to subscribe to bug-cfengine** gnUSENET newsgroup: gnu.cfengine.bug** cfengine bug reports to: bug-cfengine@gnu.orgThis list distributes, to the active maintainers of cfengine (configureBSD and System-5-like operating systems attached to a TCP/IP network),bug reports and fixes for, and suggestions for improvements to cfengine.User discussion of cfengine also occurs here.See section '* General Information about bug-* lists and reportingprogram bugs'.* help-cfengine-request@gnu.org to subscribe to help-cfengine** gnUSENET newsgroup: gnu.cfengine.help** Send contributions to: help-cfengine@gnu.orgThis list is the place for users and installers of cfengine to ask forhelp. Please send bug reports to bug-cfengine instead of posting themhere.This list is also used for announcements about cfengine and relatedprograms, and small but important patches. Announcements of cfenginereleases are also made to info-gnu@gnu.org (see above)Since help-cfengine is a large list, send it only those items thatare seriously important to many people.If source or patches that were previously posted or a simple fix isrequested in help-cfengine, please mail it to the requester. Do NOTrepost it. If you also want something that is requested, send mail tothe requester asking him to forward it to you. This kind of traffic isbest handled by e-mail, not a broadcast medium that reaches millions ofsites.See section '* General Information about help-* lists'.Also see section '* General Information about info-* lists'.* bug-gnu-smalltalk-request@gnu.org to subscribe to bug-gnu-smalltalk** gnUSENET newsgroup: gnu.smalltalk.bug** GNU Smalltalk bug reports to: bug-gnu-smalltalk@gnu.orgGNU Smalltalk is the GNU project implementation of the Smalltalk language.This list distributes, to the active maintainers of GNU Smalltalk, bugreports and fixes for, and suggestions for improvements to GNUSmalltalk. User discussion of GNU Smalltalk also occurs here.For now, new releases of GNU Smalltalk will also be announced on this list.There are no other GNU mailing lists or gnUSENET newsgroups for GNUSmalltalk.See section '* General Information about bug-* lists and reportingprogram bugs'.* st-next-request@laplace.eng.sun.com to subscribe to st-next** gnUSENET newsgroup: NONE PLANNED** Send contributions to: st-next@laplace.eng.sun.comFor people interested in working on GNU Smalltalk on the NeXT.* bug-groff-request@gnu.org to subscribe to bug-groff** gnUSENET newsgroup: gnu.groff.bug** GNU groff bug reports to: bug-groff@gnu.orggroff is the GNU project implementation, in C++, of the traditional Unixdocument formatting tools.This list distributes, to the active maintainers of groff, bug reportsand fixes for, and suggestions for improvements to groff (and itcomponent programs). User discussion of groff also occurs here.For now, new releases of groff will also be announced on this list.There are no other GNU mailing lists or gnUSENET newsgroups for groff.See section '* General Information about bug-* lists and reportingprogram bugs'.* bug-ghostscript-request@gnu.org to subscribe to bug-ghostscript** gnUSENET newsgroup: gnu.ghostscript.bug** Ghostscript bug reports to: bug-ghostscript@gnu.orgGhostscript is the GNU project implementation of a language and graphicslibrary with a remarkable similarity to PostScript.This list distributes, to the active maintainers of Ghostscript, bugreports and fixes for, and suggestions for improvements in Ghostscript.For now, new releases of Ghostscript will also be announced on this list.There are no other GNU mailing lists or gnUSENET newsgroups forGhostscript.See section '* General Information about bug-* lists and reportingprogram bugs'.* bug-gnu-utils-request@gnu.org to subscribe to bug-gnu-utils** gnUSENET newsgroup: gnu.utils.bug** GNU Utilities bug reports to: bug-gnu-utils@gnu.orgThis list distributes, to the active maintainers of these programs, bugreports and fixes for, and suggestions for improvements in GNU programsnot covered by other bug-* mailing lists/gnu.*.bug newsgroups.See section '* General Information about bug-* lists and reportingprogram bugs'.* help-gnu-utils-request@gnu.org to subscribe to help-gnu-utils** gnUSENET newsgroup: gnu.utils.help** Send contributions to: help-gnu-utils@gnu.orgThis list is the place for users and installers of GNU programs notcovered by other GNU mailing lists/gnu.* newsgroups to ask for help.Don't send bug reports to help-gnu-utils (gnu.utils.help); mail them tobug-gnu-utils@gnu.org instead.See section '* General Information about help-* lists'.* info-gnu-utils-request@gnu.org IS NOW DEFUNCT** a gnUSENET newsgroup bever existed** DEAD address: info-gnu-utils@gnu.orgThis list is dead. Announcements about GNU Utilities will be made to thelist info-gnu@gnu.org (see above).* info-cvs-request@gnu.org to subscribe to info-cvs.** USENET newsgroup: (none)** CVS discussions/questions to: info-cvs@gnu.orgThis list is for discussion and dissemination of information aboutCVS. Please check the FAQ before posting questions, however.* bug-cvs-request@gnu.org to subscribe to bug-cvs.** USENET newsgroup: (none)** CVS bug reports to: bug-cvs@gnu.orgThis list distributes bug reports, fixes, and suggestions forimprovements to the maintainers of CVS.* bug-dr-geo-request@gnu.org to subscribe to bug-dr-geo** gnUSENET newsgroup: NONE** Dr. Geo bug reports to: bug-dr-geo@gnu.orgThis list distributes bug reports for, fixes for bugs in, andsuggestions for improvements in Dr. Geo to its active developers.See section '* General Information about bug-* lists and reportingprogram bugs'.* bug-fortran-mode-request@erl.mit.edu to subscribe to bug-fortran-mode** USENET newsgroup: (none)** Fortran mode bug reports to: bug-fortran-mode@erl.mit.eduThis list collects bug reports, fixes for bugs, and suggestions forimprovements in GNU Emacs's Fortran mode (a major mode to supportediting Fortran source code).It is the place to report Fortran mode bugs by all users of Fortranmode.Always report the version number Fortran mode reports on startup as wellas the version of Emacs.There is no info-fortran-mode list. There are no USENET gateways tobug-fortran-mode at this time.* info-gnus-request@flab.fujitsu.co.jp to subscribe** gnUSENET newsgroup: NONE YET** Send contributions to: info-gnus@flab.fujitsu.co.jpThe list is intended to exchange useful information about GNUS, such asbug reports, useful hooks, and extensions of GNUS. GNUS is an NNTP-basenetwork news reader for GNU Emacs (which also works with a news spool).English and Japanese are the official languages of the list. GNUS isquite different than gnews.* info-gnus-english-request@gnu.org to subscribe** gnUSENET newsgroup: gnu.emacs.gnus** Send contributions to: info-gnus-english@gnu.orgThe list has the same charter as info-gnus. The difference is thatEnglish is the only official language of the list.info-gnus-english/gnu.emacs.gnus is forward to info-gnus, but NOTvice-versa.* info-gnews-request@ics.uci.edu to subscribe to info-gnews** gnUSENET newsgroup: gnu.emacs.gnews** Send contributions to: info-gnews@ics.uci.eduThis newsgroup is intended to exchange useful information about gnews,such as bug reports, useful hooks, and extensions of gnews. gnews is anNNTP-base network news reader for GNU Emacs (which also works a newsspool). It is quite different than GNUS.* gnu-emacs-ada-request@grebyn.com to subscribe to gnu-emacs-ada** gnUSENET newsgroup: NONE PLANNED** Gnu Emacs Ada support bug reports to: gnu-emacs-ada@grebyn.comThis list distributes bug reports for, fixes for bugs in, andsuggestions for improvements in GNU Emacs' editing support of the Adaprogramming language.There are no other GNU mailing lists or gnUSENET newsgroups for GNUEmacs' editing support of Ada.See section '* General Information about bug-* lists and reportingprogram bugs'.* bug-vm-request@uunet.uu.net to subscribe to bug-vm** gnUSENET newsgroup: gnu.emacs.vm.bug** VM mail reader bug reports to: bug-vm@uunet.uu.netThis list discusses bugs in View Mail mode for GNU Emacs, with anemphasis on beta and prerelease versions.Always report the version number of VM you are using, as well as theversion of Emacs you're running. If you believe it is significant,report the operating system used and the hardware.Subscribers to bug-vm get all info-vm messages.* info-vm-request@uunet.uu.net to subscribe to info-vm** gnUSENET newsgroup: gnu.emacs.vm.info** Send contributions to: info-vm@uunet.uu.netThis list discusses the View Mail mode for GNU Emacs, an alternative tormail mode.* supercite-request@warsaw.nlm.nih.gov to subscribe to supercite** gnUSENET newsgroup: NONE PLANNED** Send articles to: supercite@warsaw.nlm.nih.gov*** UUCP: ..!uunet!warsaw.nlm.nih.gov!supercite-requestThe supercite mailing list covers issues related to the advancedmail/news citation package called Supercite for GNU Emacs.* auc-tex-request@iesd.auc.dk to subscribe** USENET newsgroup: NONE YET** Send contributions to: auc-tex@iesd.auc.dkThe list is intended to exchange information about AUC TeX, such asbug reports, request for help, and information on currentdevelopments. AUC TeX is a much enhanced LaTeX mode for GNU Emacs.The list is unmoderated.* bug-gnu-chess-request@gnu.org to subscribe to bug-gnu-chess** gnUSENET newsgroup: gnu.chess.bug** GNU Chess bug reports to: bug-gnu-chess@gnu.orgThis list directly accesses the GNU Chess developer's group. If youhave a *BUG* to report about the program, which can also include afeature enhancement request, please send it to this list.Subscribers to bug-gnu-chess get all info-gnu-chess messages.See section '* General Information about bug-* lists and reportingprogram bugs'.* help-gnu-chess-request@gnu.org IS NOW DEFUNCT** gnUSENET newsgroup: NONE PLANNED** DEAD address: help-gnu-chess@gnu.orgThis list is dead. Use info-gnu-chess@gnu.org/gnu.chess instead.* info-gnu-chess-request@gnu.org to subscribe to info-gnu-chess** gnUSENET newsgroup: gnu.chess** Send contributions to: info-gnu-chess@gnu.org** FAQ-URL: http://www.tim-mann.org/chess.html** FAQ-Archive-name: games/chess/gnu-faq** FAQ-Posting-frequency: monthlyThis list is the place for users and installers of GNU Chess to ask forhelp. This list is also used for games played by people or otherentities against the program, and other generalized non-bug,non-enhancement data. Please send bug reports to bug-gnu-chess insteadof posting them here.This list is also used for announcements about GNU Chess and relatedprograms, and small but important patches. Announcements of GNU Chessreleases are also made to info-gnu@gnu.org (see above)Since info-gnu-chess is a large list, send it only those items thatare seriously important to many people.If source or patches that were previously posted or a simple fix isrequested in info-gnu-chess, please mail it to the requester. Do NOTrepost it. If you also want something that is requested, send mail tothe requester asking him to forward it to you. This kind of traffic isbest handled by e-mail, not a broadcast medium that reaches millions ofsites.See section '* General Information about help-* lists'.Also see section '* General Information about info-* lists'.* bug-gnu-shogi-request@gnu.org to subscribe to bug-gnu-shogi** gnUSENET newsgroup: NONE PLANNED** GNU Shogi bug reports to: bug-gnu-shogi@gnu.orgThis list directly accesses the GNU Shogi developer's group. If youhave a *BUG* to report about the program, which can also include afeature enhancement request, please send it to this list.Subscribers to bug-gnu-shogi get all info-gnu-shogi messages.See section '* General Information about bug-* lists and reportingprogram bugs'.Shogi is a game something like chess. There are several different typesof pieces, a board that is 9 by 9 squares, and the modification that acaptured piece can be reintroduced on the board by the capturing player(and used). Due to this last difference from Western chess, a Shogigame never simplifies.* bug-mcsim-request@gnu.org to subscribe to bug-mcsim** gnUSENET newsgroup: None at present.** MCSim bug reports to: bug-mcsim@gnu.orgThis list is used for bug reports concerning MCSim, a general-purpose modeling and simulation program. It is also for userdiscussion of bug fixes and patches.This list is unmoderated.See section '* General Information about bug-* lists and reportingprogram bugs'.* help-mcsim-request@gnu.org to subscribe to help-mcsim** gnUSENET newsgroup: None at present.** Send contributions to: help-mcsim@gnu.orgThis list is the place for users and installers of MCSim to ask forhelp. Please send bug reports to bug-mcsim instead of posting themhere.This list is also used for announcements about MCSim and relatedprograms, and small but important patches. Announcements of MCSimreleases are also made to info-gnu@gnu.org (see above)* bug-m4-request@gnu.org to subscribe to bug-m4** gnUSENET newsgroup: None at present.** Send contributions to: bug-m4@gnu.orgThis list is used for bug reports concerning m4, the GNU implementationof the traditional Unix macro processor. It is also for userdiscussion of bug fixes and patches.This list is unmoderated.* gpc-request@gnu.de to subscribe to gpc** gnUSENET newsgroup: None at present.** Send contributions to: gpc@gnu.deThis list is the user mailing list for GNU Pascal.*NOTE* This list was formerly at gpc@hut.fi, and moved as of 1999-05-13.Announcements will now be sent to an announcements list (see next entry)as well as to this list and info-gnu@gnu.org.* gpc-announce-request@gnu.de to subscribe to gpc-announce** gnUSENET newsgroup: None at present.** Send contributions to: gpc-announce@gnu.deThis list will have announcements to interest to users of GNU Pascal,including new releases.* autoconf-request@gnu.org to subscribe to automake** gnUSENET newsgroup: NONE PLANNED** Send contributions to: autoconf@gnu.orgThe list can be used to discuss the autoconf build system and relatedtools (eg config.guess). The discussion can range from simple "how-to"questions up to patches and future directions for this tool.* automake-request@gnu.org to subscribe to automake** gnUSENET newsgroup: NONE PLANNED** Send contributions to: automake@gnu.orgThe list can be used to discuss automake and related tools (eg libtool).The discussion can range from simple "how-to" questions up to patchesand configuration philosophy.* libtool-request@gnu.org to subscribe to libtool** gnUSENET newsgroup: NONE PLANNED** Send contributions to: libtool@gnu.orgThe list can be used to discuss development and porting of libtool, andanything else that the libtool developers might find interesting (exceptingbug-reports which have a list of their own).This list is unmoderated.* bug-libtool-request@gnu.org to subscribe to bug-libtool** gnUSENET newsgroup: NONE PLANNED** Send contributions to: bug-libtool@gnu.orgThe list can be used to submit and to discuss bugs in libtool. Thediscussion can range from bug reports and patches themselves to discourserelated to specific bugs and patches.This list is unmoderated.* libtool-commit-request@gnu.org to subscribe to libtool** gnUSENET newsgroup: NONE PLANNED** Send contributions to: libtool-commit@gnu.orgThe list distributes automatic reports of cvs commits to the libtooldevelopment sources to the list subscribers. Probably, any discussionrelated to these automatic submissions should go to the libtool list whichhas more subscribers who will see the submission.This list is unmoderated.* bug-a2ps-request@gnu.org to subscribe to bug-a2ps** gnUSENET newsgroup: NONE PLANNED** Send contributions to: bug-a2ps@gnu.orgThis list is used for bug reports concerning GNU a2ps, an Any toPostScript filter. People willing to help (debugging, or helping users)may subscribe to this list.This list is unmoderated.* a2ps-request@gnu.org to subscribe to a2ps** gnUSENET newsgroup: NONE PLANNED** Send contributions to: a2ps@gnu.orgOn this list are sent announcements about GNU a2ps --included betas--,discussions on the interface, implementations etc. It is by no means abug reporting address, and its volume should be kept moderate. To thisend, and to avoid `accidents' (bug reports and spam), this list is notmoderated but members only can post.* wget-subscribe@sunsite.auc.dk to subscribe to wget@sunsite.auc.dk** gnUSENET newsgroup: NONE PLANNED** Send contributions to: wget@sunsite.auc.dkThis list is for user discussion of wget. This list is not moderated.* help-gnu-shogi-request@gnu.org IS NOW DEFUNCT** gnUSENET newsgroup: NONE PLANNED** DEAD address: help-gnu-shogi@gnu.orgThis list is dead.* info-gnu-shogi-request@gnu.org to subscribe to info-gnu-shogi** gnUSENET newsgroup: NONE PLANNED** Send contributions to: info-gnu-shogi@gnu.orgThis list is the place for users and installers of GNU Shogi to ask forhelp. This list is also used for games played by people or otherentities against the program, and other generalized non-bug,non-enhancement data. Please send bug reports to bug-gnu-shogi insteadof posting them here.This list is also used for announcements about GNU Shogi and relatedprograms, and small but important patches. Announcements of GNU Shogireleases are also made to info-gnu@gnu.org (see above)Since info-gnu-shogi is a large list, send it only those items thatare seriously important to many people.If source or patches that were previously posted or a simple fix isrequested in info-gnu-shogi, please mail it to the requester. Do NOTrepost it. If you also want something that is requested, send mail tothe requester asking him to forward it to you. This kind of traffic isbest handled by e-mail, not a broadcast medium that reaches millions ofsites.See section '* General Information about help-* lists'.Also see section '* General Information about info-* lists'.* bug-texinfo-request@gnu.org to subscribe to bug-texinfo** gnUSENET newsgroup: NONE** GNU Texinfo bug reports to: bug-texinfo@gnu.orgThis list distributes, to the active maintainers of these programs, bugreports and fixes for, and suggestions for improvements in GNU Texinfo,both the programs and the language.See section '* General Information about bug-* lists and reportingprogram bugs'.* help-texinfo-request@gnu.org to subscribe to help-texinfo** gnUSENET newsgroup: NONE** Send contributions to: help-texinfo@gnu.orgThis list is the place for authors, users and installers of GNU Texinfoto ask for help.Don't send bug reports to help-texinfo; mail them tobug-texinfo@gnu.org instead.See section '* General Information about help-* lists'.* gnu-manual-request@a.cs.uiuc.edu IS NOW DEFUNCT** DEAD: Gnusenet newsgroup: gnu.emacs.lisp.manual** DEAD address: gnu-manual@a.cs.uiuc.edu*** DEAD UUCP address: ..!uunet!uiucdcs!gnu-manual-requestThis list and newsgroup is dead. It was a working group whosevolunteers wrote, proofread and commented on the developing GNU EmacsLisp programmers manual.Send bugs in the GNU Emacs Lisp reference manual to: lisp-manual-bugs@gnu.orglisp-manual-bugs is neither a mailing list nor a gnUSENET newsgroup.It's just a bug-reporting address.* no mailing list request** gnUSENET newsgroup: gnu.gnusenet.config** no mailing listThis newsgroup has nothing to do with GNU software, especially itsconfiguration. It exists to distribute information about theadministration and configuration of gnUSENET: the gnu.all alternativeUSENET hierarchy that carry the GNU mailing lists.Administrators of gnUSENET hosts receiving the gnu.all newsgroups arewelcome to ask questions here or via e-mail of gnu@gnu.org.* no mailing list request** gnUSENET newsgroup: gnu.gnusenet.test** no mailing listThis newsgroup has nothing to do with GNU software, especially itstesting. It exists to allow test messages to be made in gnUSENET: thegnu.all alternative USENET hierarchy that carry the GNU mailing lists.Local variables:mode: outlinefill-column: 72End:arch-tag: 6e42bba8-7532-4a23-8486-99dbc5770a8e