![[BACK]](/cvsweb/icons/back.gif){kind=icon}
Return to MAILINGLISTS CVS log ![[TXT]](/cvsweb/icons/text.gif){kind=icon}
![[DIR]](/cvsweb/icons/dir.gif){kind=icon}
Up to [Apple XNU] / GNUtools / emacs / etc|
Return to MAILINGLISTS CVS log | Up to [Apple XNU] / GNUtools / emacs / etc |
1.1 ! root 1: GNU Project Electronic Mailing Lists. Last Updated 23 Oct 91 ! 2: ! 3: Please report improvements to: [email protected] ! 4: ! 5: * GNU mailing lists are also distributed as USENET news groups ! 6: ! 7: The mailing lists are gated both ways with the gnu.all newsgroups at ! 8: ohio-state.edu. The one-to-one correspondence is indicated below. If ! 9: you don't know if your site is on USENET, ask your system administrator. ! 10: If you are a USENET site and don't get the gnu.all newsgroups, please ! 11: ask your USENET administrator to get them. If he has your feeds ask ! 12: their feeds, you should win. And everyone else wins: newsgroups make ! 13: better use of the limited bandwidth of the computer networks and your ! 14: home machine than mailing list traffic; and staying off the mailing ! 15: lists make better use of the people who maintain the lists and the ! 16: machines that the GNU people working with rms use (i.e. we have more ! 17: time to produce code!!). Thanx. ! 18: ! 19: * Getting the mailing lists directly ! 20: ! 21: If several users at your site or local network want to read a list and ! 22: you aren't a USENET site, Project GNU would prefer that you would set up ! 23: one address that redistributes locally. This reduces overhead on our ! 24: people and machines, your gateway machine, and the network(s) used to ! 25: transport the mail from us to you. ! 26: ! 27: * How to subscribe to and report bugs in mailing lists ! 28: ! 29: Send messages ABOUT these lists, such as reports of mail problems, or ! 30: requests to be added or removed, to help-gnu-emacs-request (or ! 31: info-gnu-request, bug-gdb-request, etc.), NOT to info-gnu-emacs (or ! 32: info-gnu, etc.). These <LIST_NAME>-request addresses go only to the ! 33: people who can do something about your requests or problems, and thus ! 34: avoids disturbing everyone else. ! 35: ! 36: Note that all GNU mailing lists are maintained by volunteers. They get ! 37: behind occasionally. Wait at least 3 or 4 days before asking again. ! 38: Thanks! ! 39: ! 40: Many of the GNU mailing lists are very large and are received by many ! 41: people. Please don't send them anything that is not seriously important ! 42: to all their readers. All GNU mailing lists are unmoderated, mail ! 43: reflectors, except info-gnu, info-gnu-emacs, info-gcc, info-g++ and ! 44: info-gnu-fortran. ! 45: ! 46: All addresses below are in internet format. Consult the mail guru for ! 47: your computer to figure out address syntaxes from other networks. From ! 48: UUCP machines: ! 49: ..!ucbvax!prep.ai.mit.edu!ADDRESS ! 50: ..!uunet!prep.ai.mit.edu!ADDRESS ! 51: ! 52: If a message you mail to a list is returned from a MAILER-DAEMON (often ! 53: with the line: ! 54: ----- Transcript of session follows ----- ! 55: don't resend the message to the list. All this return means is that ! 56: your original message failed to reach a few addresses on the list. Such ! 57: messages are NEVER a reason to resend a piece of mail a 2nd time. This ! 58: just bothers all (less the few delivery failures (which will probably ! 59: just fail again!)) of the readers of the list with a message they have ! 60: already seen. It also wastes computer and network resources. ! 61: ! 62: It is appropriate to send these to the -request address for a list, and ! 63: ask them to check the problem out. ! 64: ! 65: * Send Specific Requests for Information to: [email protected] ! 66: ! 67: Specific requests for information about obtaining GNU software, or GNU ! 68: activities in Cambridge and elsewhere can be directed to: ! 69: [email protected] ! 70: ! 71: * General Information about all lists ! 72: ! 73: Please keep each message under 40,000 characters. Some mailers bounce ! 74: messages that are longer than this. ! 75: ! 76: Most of the time, when you reply to a message sent to a list, the reply ! 77: should not go to the list. But most mail reading programs supply, by ! 78: default, all the recipients of the original as recipients of the reply. ! 79: Make a point of deleting the list address from the header when it does ! 80: not belong. This prevents bothering all readers of a list, and reduces ! 81: network congestion. ! 82: ! 83: The GNU mailing lists and newsgroups, like the GNU project itself, exist ! 84: to promote the freedom to share software. So don't use these lists to ! 85: promote or recommend non-free software. (Using them to post ordering ! 86: information is the ultimate faux pas.) If there is no free program to ! 87: do a certain task, then somebody should write one! ! 88: ! 89: * General Information about info-* lists ! 90: ! 91: These lists and their newsgroups are meant for important announcements. ! 92: Since the GNU project uses software development as a means for social ! 93: change, the announcements may be technical or political. ! 94: ! 95: Most GNU projects info-* lists (and their corresponding gnu.*.announce ! 96: newsgroups) are moderated to keep their content significant and ! 97: relevant. If you have a bug to report, send it to the bug-* list. If ! 98: you need help on something else and the help-* list exists, ask it. ! 99: ! 100: See section '* General Information about all lists'. ! 101: ! 102: * General Information about help-* lists ! 103: ! 104: These lists (and their newsgroups) exist for anyone to ask questions ! 105: about the GNU software that the list deals with. The lists are read by ! 106: people who are willing to take the time to help other users. ! 107: ! 108: When you answer the questions that people ask on the help-* lists, keep ! 109: in mind that you shouldn't answer by promoting a proprietary program as ! 110: a solution. The only real solutions are the ones all the readers can ! 111: share. ! 112: ! 113: See section '* General Information about all lists'. ! 114: ! 115: * General Information about bug-* lists and reporting program bugs ! 116: ! 117: If you think something is a bug in a program, it might be one; or, it ! 118: might be a misunderstanding or even a feature. Before beginning to ! 119: report bugs, please read the section ``Reporting Emacs Bugs'' toward the ! 120: end of the GNU Emacs reference manual (or node Emacs/Bugs in Emacs's ! 121: built-in Info system) for a discussion of how and when to send in bug ! 122: reports. For GNU programs other than GNU Emacs, also consult their ! 123: documentation for their bug reporting procedures. Always include the ! 124: version number of the GNU program, as well as the operating system and ! 125: machine the program was ran on (if the program doesn't have a version ! 126: number, send the date of the latest entry in the file ChangeLog). For ! 127: GNU Emacs bugs, type "M-x emacs-version". A debugger backtrace of any ! 128: core dump, can also be useful. Be careful to separate out hypothesis ! 129: from fact! For bugs in GNU Emacs lisp, set variable debug-on-error to ! 130: t, and re-enter the command(s) that cause the error message; Emacs will ! 131: pop up a debug buffer if something is wrong; please include a copy of ! 132: the buffer in your bug report. ! 133: ! 134: Please don't send in a patch without a test case to illustrate the ! 135: problem the patch is supposed to fix. Sometimes the patches aren't ! 136: correct or aren't the best way to do the job, and without a test case ! 137: there is no way to debug an alternate fix. ! 138: ! 139: The purpose of reporting a bug is to enable the bug to be fixed for the ! 140: sake of the whole community of users. You may or may not receive a ! 141: response; the maintainers will send one if that helps them find or ! 142: verify a fix. Most GNU maintainers are volunteers and all are ! 143: overworked; they don't have time to help individuals and still fix the ! 144: bugs and make the improvements that everyone wants. If you want help ! 145: for yourself in particular, you may have to hire someone. The GNU ! 146: project maintains a list of people providing such services. It is ! 147: distributed with GNU Emacs in file etc/SERVICE, and can be requested ! 148: from [email protected]. ! 149: ! 150: Anything addressed to the implementors and maintainers of a GNU program ! 151: via a bug-* list, should NOT be sent to the corresponding info-* or ! 152: help-* list. ! 153: ! 154: Please DON'T post your bug reports on the gnu.* newsgroups! Mail them ! 155: to bug-*@prep instead! At first sight, it seems to make no difference: ! 156: anything sent to one will be propagated to the other; but if you post on ! 157: the newsgroup, the information about how to reach you is lost in the ! 158: message that goes on the mailing list. It can be very important to know ! 159: how to reach you if there is anything in the bug report that we don't ! 160: understand. Bug reports also reach the GNU maintainers quickest when ! 161: they are sent to the bug-* mailing list submittal address. ! 162: ! 163: And please DON'T post your GNU bug reports to comp.* or other non gnu.* ! 164: newsgroups, they never make it to the GNU maintainers at all. Please ! 165: mail them to bug-*@prep instead! ! 166: ! 167: See section '* General Information about all lists'. ! 168: ! 169: * [email protected] to subscribe to info-gnu ! 170: ** gnUSENET newsgroup: gnu.announce ! 171: ** Send announcements to: [email protected] ! 172: ! 173: This list distributes progress reports on the GNU Project. It is also ! 174: used by the GNU Project to ask people for various kinds of help. It is ! 175: NOT for general discussion. ! 176: ! 177: The list is filtered to remove items meant for info-gnu-request, that ! 178: can be answered by the moderator without bothering the list, or should ! 179: have been sent to another list. ! 180: ! 181: See section '* General Information about info-* lists'. ! 182: ! 183: * [email protected] to subscribe to gnu-misc-discuss ! 184: ** gnUSENET newsgroup: gnu.misc.discuss ! 185: ** Send contributions to: [email protected] ! 186: ! 187: This list is for serious discussion of freed software, the GNU ! 188: Project, the GNU Manifesto and their implications. It's THE place for ! 189: discussion that is not appropriate in the other GNU mailing lists and ! 190: gnUSENET newsgroups. ! 191: ! 192: Flaming is out of place. Tit-for-tat is not welcome. Repetition ! 193: should not occur. ! 194: ! 195: Good READING and writing are expected. Before posting, wait a while, ! 196: cool off, and think. ! 197: ! 198: Don't trust pronouncements made on gnu-misc-discuss about what GNU is, ! 199: what FSF position is, what the GNU General Public License is, etc., ! 200: unless they are made by someone you know is well connected with GNU and ! 201: are sure the message is not forged. ! 202: ! 203: USENET and gnUSENET readers are expected to have read ALL the articles ! 204: in news.announce.newusers before posting. If news.announce.newusers is ! 205: empty at your site, wait (the articles are posted monthly), your posting ! 206: isn't that urgent! Readers on the Internet can anonymous ftp these ! 207: articles from wsmr-simtel20.army.mil under directory ! 208: PD2:<UNIX-C.USENET>. ! 209: ! 210: Someone from the Free Software Foundation will attempt to follow this ! 211: group as time and volume permits. ! 212: ! 213: Remember, "GNUs Not Unix" and "gnUSENET is Not USENET". We have ! 214: higher standards! ! 215: ! 216: Note that sending technical questions about specific GNU software to ! 217: gnu-misc-discuss is likely to be less useful than sending them to the ! 218: appropriate mailing list or gnUSENET newsgroup, since more technical ! 219: people read those. ! 220: ! 221: * [email protected] to subscribe to bug-gnu-emacs ! 222: ** gnUSENET newsgroup: gnu.emacs.bug ! 223: ** Gnu Emacs bug reports to: [email protected] ! 224: ! 225: This list distributes, to the active maintainers of GNU Emacs, bug ! 226: reports and fixes for, and suggestions for improvements in GNU Emacs. ! 227: It is the place to report GNU Emacs bugs by all users of GNU Emacs. ! 228: ! 229: Send bugs in the GNU Emacs Lisp reference manual to: ! 230: [email protected] ! 231: ! 232: lisp-manual-bugs is neither a mailing list nor a gnUSENET newsgroup. ! 233: It's just a bug-reporting address. ! 234: ! 235: Subscribers to bug-gnu-emacs automatically receive all ! 236: info-gnu-emacs messages. ! 237: ! 238: See section '* General Information about bug-* lists and reporting ! 239: program bugs'. ! 240: ! 241: * [email protected] to subscribe to gnu-emacs-sources ! 242: ** gnUSENET newsgroup: gnu.emacs.sources ! 243: ** Gnu Emacs source code to: [email protected] ! 244: ! 245: This list/newsgroup will be for the posting, by their authors, of lisp ! 246: and C sources and patches that improve GNU Emacs. Its contents will ! 247: be reviewed by FSF for inclusion in future releases of GNU Emacs. ! 248: ! 249: Please do NOT discuss or request source code here. Use ! 250: help-gnu-emacs/gnu.emacs.help for those purposes. This allows the ! 251: automatic archiving of sources posted to this list/newsgroup. ! 252: ! 253: Please do NOT post such sources to any other GNU mailing list (e.g ! 254: help-gnu-emacs) or gnUSENET newsgroups (e.g. gnu.emacs.help). It's up ! 255: to each poster to decide whether to cross-post to any non-gnUSENET ! 256: newsgroup (e.g. comp.emacs or vmsnet.sources). ! 257: ! 258: Please do NOT announce that you have posted source code to ! 259: gnu.emacs.sources to any other GNU mailing list (e.g. help-gnu-emacs) or ! 260: gnUSENET newsgroups (e.g. gnu.emacs.help). People who want to keep up ! 261: with sources will read this list/newsgroup. It's up to each poster to ! 262: decide whether to announce a gnu.emacs.sources article in any ! 263: non-gnUSENET newsgroup (e.g comp.emacs or comp.sources.d). ! 264: ! 265: If source or patches that were previously posted or a simple fix is ! 266: requested in help-gnu-emacs, please mail it to the requester. Do NOT ! 267: repost it. If you also want something that is requested, send mail to ! 268: the requester asking him to forward it to you. This kind of traffic is ! 269: best handled by e-mail, not by a broadcast medium that reaches thousands ! 270: of sites. ! 271: ! 272: If the source is very long (>10k bytes) send mail offering to send it. ! 273: This prevents the requester from getting many redundant copies and saves ! 274: network bandwidth. ! 275: ! 276: * [email protected] to subscribe to help-gnu-emacs ! 277: ** gnUSENET newsgroup: gnu.emacs.help (and one-way into comp.emacs) ! 278: ** Send contributions to: [email protected] ! 279: ! 280: This list is the place for users and installers of GNU Emacs to ask for ! 281: help. Please send bug reports to bug-gnu-emacs instead of posting them ! 282: here. ! 283: ! 284: Since help-gnu-emacs is a very large list, send it only those items that ! 285: are seriously important to many people. ! 286: ! 287: If source or patches that were previously posted or a simple fix is ! 288: requested in help-gnu-emacs, please mail it to the requester. Do NOT ! 289: repost it. If you also want something that is requested, send mail to ! 290: the requester asking him to forward it to you. This kind of traffic is ! 291: best handled by e-mail, not a broadcast medium that reaches thousands of ! 292: sites. ! 293: ! 294: This list is also gated one way to USENET's newsgroup comp.emacs (once ! 295: known as net.emacs). This one-way gating is done for users whose sites ! 296: get comp.emacs, but not gnu.emacs.help. Users at non-USENET sites may ! 297: receive all articles from comp.emacs by making their request to: ! 298: [email protected] ! 299: ! 300: If Emacs crashes, or if you build Emacs following the standard procedure ! 301: on a system which Emacs is supposed to work on (see etc/MACHINES) and it ! 302: does not work at all, or if an editing command does not behave as it is ! 303: documented to behave, this is a bug. Don't send bug reports to ! 304: help-gnu-emacs (gnu.emacs.help) or post them to comp.emacs; mail them to ! 305: bug-gnu-emacs instead. ! 306: ! 307: See section '* General Information about help-* lists'. ! 308: ! 309: * [email protected] to subscribe to info-gnu-emacs ! 310: ** gnUSENET newsgroup: gnu.emacs.announce (and one-way into comp.emacs) ! 311: ** Send announcements to: [email protected] ! 312: ! 313: This list distributes announcements and progress reports on GNU Emacs. ! 314: It is NOT for general discussion; please use help-gnu-emacs for that. ! 315: ! 316: The list is filtered to remove items meant for info-gnu-emacs-request, ! 317: that can be answered by the moderator without bothering the list, or ! 318: should have been sent to another list. ! 319: ! 320: info-gnu-emacs is also gated one way to USENET's newsgroup comp.emacs ! 321: (once known as net.emacs). This one-way gating is done for users whose ! 322: sites get comp.emacs, but not gnu.emacs.announce. Users at non-USENET ! 323: sites may receive all articles from comp.emacs by making their request ! 324: to: [email protected] ! 325: ! 326: Do not report GNU Emacs bugs to info-gnu-emacs or comp.emacs, instead ! 327: mail them to [email protected]. ! 328: ! 329: See section '* General Information about info-* lists'. ! 330: ! 331: * [email protected] to subscribe to vms-gnu-emacs ! 332: ** gnUSENET newsgroup: gnu.emacs.vms ! 333: ** Send contributions to: [email protected] ! 334: *** UUCP: ..!uunet!harvard!vms-gnu-emacs-request ! 335: ! 336: This list was a working group who did the initial port of GNU Emacs to ! 337: the VMS operating system. It still discusses problems and solutions to ! 338: the VMS port and the distribution of it. ! 339: ! 340: * [email protected] to subscribe to bug-bash ! 341: ** gnUSENET newsgroup: gnu.bash.bug ! 342: ** BASH bug reports to: [email protected] ! 343: ! 344: This list distributes, to the active maintainers of BASH (the Bourne ! 345: Again SHell), bug reports and fixes for, and suggestions for ! 346: improvements in BASH. It is the place to report BASH bugs by all users ! 347: of BASH. ! 348: ! 349: Always report the version number of the operating system, hardware, and ! 350: bash (flag -version on startup or check the variable $BASH_VERSION in a ! 351: running bash). ! 352: ! 353: There are no other GNU mailing lists or gnUSENET newsgroups for BASH. ! 354: ! 355: See section '* General Information about bug-* lists and reporting ! 356: program bugs'. ! 357: ! 358: * [email protected] to subscribe to bug-gdb ! 359: ** gnUSENET newsgroup: gnu.gdb.bug ! 360: ** GDB bug reports to: [email protected] ! 361: ! 362: This list distributes, to the active maintainers of GDB (Gnu's ! 363: DeBugger), bug reports and fixes for, and suggestions for improvements ! 364: in GDB. It is the place to report GDB bugs by all users of GDB. ! 365: ! 366: There are no other GNU mailing lists or gnUSENET newsgroups for GDB. ! 367: ! 368: See section '* General Information about bug-* lists and reporting ! 369: program bugs'. ! 370: ! 371: * [email protected] to subscribe to bug-gcc ! 372: ** gnUSENET newsgroup: gnu.gcc.bug ! 373: ** GCC bug reports to: [email protected] ! 374: ! 375: This list distributes bug reports for, fixes for bugs in, and ! 376: suggestions for improvements in the GNU C Compiler to its active ! 377: developers. It is the place to report GCC bugs by all testers of GCC. ! 378: The GNU C Compiler still has bugs in it, and is not quite ready for ! 379: everyday use. ! 380: ! 381: Please don't send in a patch without a test case to illustrate the ! 382: problem the patch is supposed to fix. Sometimes the patches aren't ! 383: correct or aren't the best way to do the job, and without a test case ! 384: there is no way to debug an alternate fix. ! 385: ! 386: The most convenient form of test case is a piece of cpp output that can ! 387: be passed directly to cc1. Preferably written in C, not C++. ! 388: ! 389: Subscribers to bug-gcc automatically receive all info-gcc messages. ! 390: ! 391: See section '* General Information about bug-* lists and reporting ! 392: program bugs'. ! 393: ! 394: * [email protected] to subscribe to help-gcc ! 395: ** gnUSENET newsgroup: gnu.gcc.help ! 396: ** Send contributions to: [email protected] ! 397: ! 398: This list is the place for users and installers of the GNU C Compiler to ! 399: ask for help. ! 400: ! 401: If gcc crashes, or if you build gcc following the standard procedure on ! 402: a system which gcc is supposed to work on (see config.gcc) and it does ! 403: not work at all, or if an command line option does not behave as it is ! 404: documented to behave, this is a bug. Don't send bug reports to help-gcc ! 405: (gnu.gcc.help); mail them to bug-gcc instead. ! 406: ! 407: See section '* General Information about help-* lists'. ! 408: ! 409: * [email protected] to subscribe to info-gcc ! 410: ** gnUSENET newsgroup: gnu.gcc.announce ! 411: ** Send announcements to: [email protected] ! 412: ! 413: This list distributes announcements and progress reports on the GNU C ! 414: Compiler. It is NOT for general discussion; please use help-gcc for ! 415: that. ! 416: ! 417: The list is filtered to remove items meant for info-gcc-request, that ! 418: can be answered by the moderator without bothering the list, or should ! 419: have been sent to another list. ! 420: ! 421: See section '* General Information about info-* lists'. ! 422: ! 423: * [email protected] to subscribe to bug-g++ ! 424: ** gnUSENET newsgroup: gnu.g++.bug ! 425: ** G++ bug reports to: [email protected] ! 426: ! 427: This list distributes bug reports for, fixes for bugs in, and ! 428: suggestions for improvements in the GNU C++ Compiler to its active ! 429: developers. It is the place to report G++ bugs by all testers of G++. ! 430: ! 431: G++ uses the GNU C-Compiler back end. Active developers may wish to ! 432: subscribe to [email protected] as well. ! 433: ! 434: Subscribers to bug-g++ automatically receive all info-g++ messages. ! 435: ! 436: See section '* General Information about bug-* lists and reporting ! 437: program bugs'. ! 438: ! 439: * [email protected] to subscribe to help-g++ ! 440: ** gnUSENET newsgroup: gnu.g++.help (and one-way into comp.lang.c++) ! 441: ** Send contributions to: [email protected] ! 442: ! 443: This list is the place for users and installers of the GNU C++ Compiler ! 444: to ask for help. Please send bug reports to bug-g++ instead of posting ! 445: them here. ! 446: ! 447: help-g++ is also gated one way to USENET's newsgroup comp.lang.c++. ! 448: This one-way gating is done for users whose sites get comp.lang.c++, but ! 449: not gnu.g++.help. ! 450: ! 451: If g++ crashes, or if you build g++ following the standard procedure on ! 452: a system which g++ is supposed to work on (see config.g++) and it does ! 453: not work at all, or if an command line option does not behave as it is ! 454: documented to behave, this is a bug. Don't send bug reports to help-g++ ! 455: (gnu.g++.help) or post them to comp.lang.c++; mail them to bug-g++ ! 456: instead. ! 457: ! 458: See section '* General Information about help-* lists'. ! 459: ! 460: * [email protected] to subscribe to info-g++ ! 461: ** gnUSENET newsgroup: gnu.g++.announce (and one-way into comp.lang.c++) ! 462: ** Send announcements to: [email protected] ! 463: ! 464: This list distributes announcements and progress reports on the GNU C++ ! 465: Compiler. It is NOT for general discussion; please use help-g++ for ! 466: that. ! 467: ! 468: The list is filtered to remove items meant for info-g++-request, that ! 469: can be answered by the moderator without bothering the list, or should ! 470: have been sent to another list. ! 471: ! 472: It is also gated one way to USENET's newsgroup comp.lang.c++. This ! 473: one-way gating is done for users whose sites get comp.lang.c++, but not ! 474: gnu.g++.announce. ! 475: ! 476: Do not report g++ bugs to info-g++ or comp.lang.c++, mail them to ! 477: [email protected] instead. ! 478: ! 479: See section '* General Information about info-* lists'. ! 480: ! 481: * [email protected] to subscribe to bug-lib-g++ ! 482: ** gnUSENET newsgroup: gnu.g++.lib.bug ! 483: ** lib-g++ bug reports to: [email protected] ! 484: ! 485: This list distributes, to the active maintainers of lib-g++ (GNU's ! 486: library for C++), bug reports and fixes for, and suggestions for ! 487: improvements in lib-g++. It is the place to report lib-g++ bugs by all ! 488: users of lib-g++. ! 489: ! 490: Announcements of new releases of lib-g++ are made on both info-g++ and ! 491: bug-lib-g++. ! 492: ! 493: There are no other GNU mailing lists or gnUSENET newsgroups for the G++ ! 494: Library. ! 495: ! 496: See section '* General Information about bug-* lists and reporting ! 497: program bugs'. ! 498: ! 499: * [email protected] to subscribe to info-gnu-fortran ! 500: ** gnUSENET newsgroup: NONE YET ! 501: ** Send contributions to: [email protected] ! 502: ! 503: This list is for progress reports about the GNU Fortran compiler. In ! 504: the future it will also be used for release notices. ! 505: ! 506: The list is filtered to remove items meant for info-gnu-fortran-request, ! 507: that can be answered by the moderator without bothering the list, or ! 508: should have been sent to another list. ! 509: ! 510: See section '* General Information about info-* lists'. ! 511: ! 512: There are no other GNU mailing lists or gnUSENET newsgroups for GNU ! 513: Fortran (yet). ! 514: ! 515: * [email protected] to subscribe to bug-gnu-smalltalk ! 516: ** gnUSENET newsgroup: gnu.smalltalk.bug ! 517: ** GNU Smalltalk bug reports to: [email protected] ! 518: ! 519: GNU Smalltalk is the GNU project implementation of the Smalltalk language. ! 520: ! 521: This list distributes, to the active maintainers of GNU Smalltalk, bug ! 522: reports and fixes for, and suggestions for improvements to GNU ! 523: Smalltalk. It is the place to report bugs in GNU Smalltalk by all users ! 524: of the program. ! 525: ! 526: For now, new releases of GNU Smalltalk will also be announced on this list. ! 527: ! 528: There are no other GNU mailing lists or gnUSENET newsgroups for GNU ! 529: Smalltalk. ! 530: ! 531: See section '* General Information about bug-* lists and reporting ! 532: program bugs'. ! 533: ! 534: * [email protected] to subscribe to bug-groff ! 535: ** gnUSENET newsgroup: gnu.groff.bug ! 536: ** GNU groff bug reports to: [email protected] ! 537: ! 538: groff is the GNU project implementation, in C++, of the traditional ! 539: Unix document formatting tools. As of June 1990 it includes troff, ! 540: pic, tbl, eqn, man macros, a PostScript driver, a driver which ! 541: produces TeX dvi format and a driver for typewriter-like devices. A ! 542: modified version of the Berkeley me macros and an enhanced version of ! 543: the X11R4 xditview are also included. ! 544: ! 545: This list distributes, to the active maintainers of groff, bug reports ! 546: and fixes for, and suggestions for improvements to groff (and it ! 547: component programs). It is the place for all users of groff to report ! 548: bugs. ! 549: ! 550: For now, new releases of groff will also be announced on this list. ! 551: ! 552: There are no other GNU mailing lists or gnUSENET newsgroups for groff. ! 553: ! 554: See section '* General Information about bug-* lists and reporting ! 555: program bugs'. ! 556: ! 557: * [email protected] to subscribe to bug-ghostscript ! 558: ** gnUSENET newsgroup: gnu.ghostscript.bug ! 559: ** Ghostscript bug reports to: [email protected] ! 560: ! 561: GhostScript is the GNU project implementation of a language and graphics ! 562: library with a remarkable similarity to PostScript. ! 563: ! 564: This list distributes, to the active maintainers of Ghostscript, bug ! 565: reports and fixes for, and suggestions for improvements in Ghostscript. It ! 566: is the place to report bugs in Ghostscript by all users of them. ! 567: ! 568: For now, new releases of Ghostscript will also be announced on this list. ! 569: ! 570: There are no other GNU mailing lists or gnUSENET newsgroups for ! 571: GhostScript. ! 572: ! 573: See section '* General Information about bug-* lists and reporting ! 574: program bugs'. ! 575: ! 576: * [email protected] to subscribe to info-gnu-chess ! 577: ** gnUSENET newsgroup: gnu.chess ! 578: ** Send contributions to: [email protected] ! 579: ! 580: This list reports new releases and information about the program GNU ! 581: Chess. ! 582: ! 583: See section '* General Information about info-* lists'. ! 584: ! 585: * [email protected] to subscribe to bug-gnu-utils ! 586: ** gnUSENET newsgroup: gnu.utils.bug ! 587: ** GNU Utilities bug reports to: [email protected] ! 588: ! 589: This list distributes, to the active maintainers of these programs, bug ! 590: reports and fixes for, and suggestions for improvements in GNU programs ! 591: not covered by other bug-* mailing lists/gnu.*.bug newsgroups. It is ! 592: the place to report bugs in these GNU programs by all users of them. ! 593: ! 594: There are no other GNU mailing lists or gnUSENET newsgroups for these ! 595: GNU utilities. ! 596: ! 597: See section '* General Information about bug-* lists and reporting ! 598: program bugs'. ! 599: ! 600: * [email protected] to subscribe to bug-fortran-mode ! 601: ** USENET newsgroup: (none) ! 602: ** Fortran mode bug reports to: [email protected] ! 603: ! 604: This list collects bug reports, fixes for bugs, and suggestions for ! 605: improvements in GNU Emacs's Fortran mode (a major mode to support ! 606: editing Fortran source code). ! 607: ! 608: It is the place to report Fortran mode bugs by all users of Fortran ! 609: mode. ! 610: ! 611: Always report the version number Fortran mode reports on startup as well ! 612: as the version of Emacs. ! 613: ! 614: There is no info-fortran-mode list. There are no USENET gateways to ! 615: bug-fortran-mode at this time. ! 616: ! 617: * info-gnus-request%[email protected] to subscribe ! 618: ** gnUSENET newsgroup: NONE YET ! 619: ** Send contributions to: info-gnus%[email protected] ! 620: ! 621: The list is intended to exchange useful information about GNUS, such as ! 622: bug reports, useful hooks, and extensions of GNUS. GNUS is an NNTP-base ! 623: network news reader for GNU Emacs (which also works with a news spool). ! 624: English and Japanese are the official languages of the list. GNUS is ! 625: quite different than gnews. ! 626: ! 627: * [email protected] to subscribe ! 628: ** gnUSENET newsgroup: gnu.emacs.gnus ! 629: ** Send contributions to: [email protected] ! 630: ! 631: The list has the same charter as info-gnus. The difference is that ! 632: English is the only official language of the list. ! 633: ! 634: info-gnus-english/gnu.emacs.gnus is forward to info-gnus, but NOT ! 635: vice-versa. ! 636: ! 637: * [email protected] to subscribe to info-gnews ! 638: ** gnUSENET newsgroup: gnu.emacs.gnews ! 639: ** Send contributions to: [email protected] ! 640: ! 641: This newsgroup is intended to exchange useful information about gnews, ! 642: such as bug reports, useful hooks, and extensions of gnews. gnews is an ! 643: NNTP-base network news reader for GNU Emacs (which also works a news ! 644: spool). It is quite different than GNUS. ! 645: ! 646: * [email protected] to subscribe to gnu-emacs-ada ! 647: ** gnUSENET newsgroup: NONE PLANNED ! 648: ** Gnu Emacs Ada support bug reports to: [email protected] ! 649: ! 650: This list distributes bug reports for, fixes for bugs in, and ! 651: suggestions for improvements in GNU Emacs' editing support of the Ada ! 652: programming language. ! 653: ! 654: There are no other GNU mailing lists or gnUSENET newsgroups for GNU ! 655: Emacs' editing support of Ada. ! 656: ! 657: See section '* General Information about bug-* lists and reporting ! 658: program bugs'. ! 659: ! 660: * [email protected] to subscribe to bug-vm ! 661: ** gnUSENET newsgroup: NONE ! 662: ** VM mail reader bug reports to: [email protected] ! 663: ! 664: This list discusses bugs in View Mail mode for GNU Emacs, with an ! 665: emphasis on beta and prerelease versions. It is the place to report ! 666: bugs in VM. ! 667: ! 668: Always report the version number of VM you are using, as well as the ! 669: version of Emacs you're running. If you believe it is significant, ! 670: report the operating system used and the hardware. ! 671: ! 672: Subscribers to bug-vm automatically receive all info-vm messages. ! 673: ! 674: * [email protected] to subscribe to info-vm ! 675: ** gnUSENET newsgroup: NONE ! 676: ** Send contributions to: [email protected] ! 677: ! 678: This list dicusses the View Mail mode for GNU Emacs, an alternative to ! 679: rmail mode. ! 680: ! 681: * [email protected] to subscribe to supercite ! 682: ** gnUSENET newsgroup: NONE PLANNED ! 683: ** Send articles to: [email protected] ! 684: *** UUCP: ..!uunet!warsaw.nlm.nih.gov!supercite-request ! 685: ! 686: The supercite mailing list covers issues related to the advanced ! 687: mail/news citation package called Supercite for GNU Emacs. ! 688: ! 689: * [email protected] to subscribe to bug-gnu960 ! 690: ** gnUSENET newsgroup: NONE PLANNED ! 691: ** Intel 960 Port bug reports to: [email protected] ! 692: ! 693: This list distributes bug reports for, fixes for bugs in, and ! 694: suggestions for improvements in Intel's port of GNU software to the ! 695: Intel 960 microprocessor. ! 696: ! 697: You can also fax to: GNU/960 - 1-503-696-4930. ! 698: ! 699: There are no other GNU mailing lists or gnUSENET newsgroups for Intel's ! 700: port of GNU software to the Intel 960 microprocessor. ! 701: ! 702: See section '* General Information about bug-* lists and reporting ! 703: program bugs'. ! 704: ! 705: * [email protected] IS NOW DEFUNCT ! 706: ** DEAD: Gnusenet newsgroup: gnu.emacs.lisp.manual ! 707: ** DEAD address: [email protected] ! 708: *** DEAD UUCP address: ..!uunet!uiucdcs!gnu-manual-request ! 709: ! 710: This list and newsgroup is dead. It was a working group whose ! 711: volunteers wrote, proofread and commented on the developing GNU Emacs ! 712: Lisp programmers manual. ! 713: ! 714: Send bugs in the GNU Emacs Lisp reference manual to: ! 715: [email protected] ! 716: ! 717: lisp-manual-bugs is neither a mailing list nor a gnUSENET newsgroup. ! 718: It's just a bug-reporting address. ! 719: ! 720: * no mailing list request ! 721: ** gnUSENET newsgroup: gnu.gnusenet.config ! 722: ** no mailing list ! 723: ! 724: This newsgroup has nothing to do with GNU software, especially its ! 725: configuration. It's exists to distribute information about the ! 726: administration and configuration of gnUSENET: the gnu.all alternative ! 727: USENET hierarchy that carry the GNU mailing lists. ! 728: ! 729: Administrators of gnUSENET hosts receiving the gnu.all newsgroups are ! 730: welcome to ask questions here or via e-mail of [email protected]. ! 731: ! 732: * no mailing list request ! 733: ** gnUSENET newsgroup: gnu.gnusenet.test ! 734: ** no mailing list ! 735: ! 736: This newsgroup has nothing to do with GNU software, especially its ! 737: testing. It's exists to allow test messages to be made in gnUSENET: the ! 738: gnu.all alternative USENET hierarchy that carry the GNU mailing lists. ! 739: ! 740: Local variables: ! 741: mode: outline ! 742: fill-column: 72 ! 743: End:
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.