![[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 [CSRG BSD Unix] / 43BSDReno / contrib / emacs-18.55 / etc|
Return to MAILINGLISTS CVS log | Up to [CSRG BSD Unix] / 43BSDReno / contrib / emacs-18.55 / etc |
1.1 ! root 1: GNU Project electronic mailing lists. Last Updated 20 Feb 1989 ! 2: ! 3: * GNU mailing lists are also distributed as USENET news groups ! 4: ! 5: The mailing lists are gated both ways with the gnu.all newsgroups at ! 6: ohio-state.edu. The one-to-one correspondence is indicated below. If ! 7: you don't know if your site is on USENET, ask your system administrator. ! 8: If you are a USENET site and don't get the gnu.all newsgroups, please ! 9: ask your USENET administrator to get them. If he has your feeds ask ! 10: their feeds, you should win. And everyone else wins: newsgroups make ! 11: better use of the limited bandwidth of the computer networks and your ! 12: home machine than mailing list traffic; and staying off the mailing ! 13: lists make better use of the people who maintain the lists and the ! 14: machines that the GNU people working with rms use (i.e. we have more ! 15: time to produce code!!). Thanx. ! 16: ! 17: * Getting the mailing lists directly ! 18: ! 19: If several users at your site or local network would like to read a list ! 20: and you aren't a USENET site, Project GNU would prefer if you would set ! 21: up one address that redistributes locally. This reduces overhead on our ! 22: machine, your gateway machine, and the network(s) used to transport the ! 23: mail from us to you. ! 24: ! 25: * How to subscribe and reporting bugs in the mailing lists ! 26: ! 27: Send messages ABOUT these lists, such as reports of mail problems, or ! 28: requests to be added or removed, to info-gnu-emacs-request (or ! 29: info-gnu-request, bug-gdb-request, etc.), NOT to info-gnu-emacs (or ! 30: info-gnu, etc.). These <LIST_NAME>-request addresses go only to the ! 31: people who can do something about your requests or problems, and thus ! 32: avoids disturbing everyone else. ! 33: ! 34: All GNU mailing lists are unmoderated, mail reflectors, except info-gnu. ! 35: They are very large lists, please don't send them anything that is not ! 36: seriously important to many people. ! 37: ! 38: All addresses below are in internet format. Consult the mail guru for ! 39: your computer to figure out address syntaxes from other networks. From ! 40: UUCP machines: ! 41: ..!ucbvax!prep.ai.mit.edu!ADDRESS ! 42: ..!mit-eddie!mit-prep!ADDRESS ! 43: ! 44: If a message you mail to a list is returned from a MAILER-DAEMON (often ! 45: with the line: ! 46: ----- Transcript of session follows ----- ! 47: ), don't resend the message to the list. All this return means is that ! 48: your original message failed to reach a few addresses on the list. Such ! 49: messages are NEVER a reason to resend a piece of mail a 2nd time. This ! 50: just bothers all (N - few) of the readers of the list with a message ! 51: they have already seen. It also wastes computer and network resources. ! 52: ! 53: It is appropriate to send these to the -request address for a list, and ! 54: ask them to check the problem out. ! 55: ! 56: * Specific Requests for Information to: [email protected] ! 57: ! 58: Specific requests for information about obtaining GNU software, or GNU ! 59: activities in Cambridge and elsewhere can be directed to: ! 60: [email protected] ! 61: ! 62: * General Information about info-* lists ! 63: ! 64: Most of the time, when you reply to a message sent to an info-* list, ! 65: the reply should not go to the info-* list. But most mailer reading ! 66: programs supply all the recipients of the original as recipients of the ! 67: reply, by default. Make a point of deleting the info-* address from the ! 68: list when it does not belong. This prevents bothering all readers of a ! 69: list, and reduces network congestion. ! 70: ! 71: * General Information about bug-* lists and reporting program bugs ! 72: ! 73: If you think something is a bug in a program, it might be one; or, it ! 74: might be a misunderstanding or even a feature. Before beginning to ! 75: report bugs, please read the section ``Reporting Emacs Bugs'' toward the ! 76: end of the GNU Emacs reference manual (or GEM's built-in Info system) ! 77: for a discussion of how and when to send in bug reports. Always include ! 78: the version number of the program, as well as the operating system and ! 79: machine the program was ran on. A debugger backtrace of any core dump, ! 80: can also be useful. Be careful to separate out hypothesis from fact! ! 81: For GNU Emacs bugs, type "M-x emacs-version". For bugs in GNU Emacs ! 82: lisp, set variable debug-on-error to t, and re-enter the command(s) that ! 83: cause the error message; GEM will pop up a debug buffer if something is ! 84: wrong; please include a copy of the buffer in your bug report. ! 85: ! 86: Do not expect an answer for a bug report, except sometimes in the form ! 87: of a fix for the bug in the next release. Reporting a bug is done to ! 88: get the bug fixed for everyone. Likewise, we maintainers fix bugs in ! 89: order to help the entire community. We see no such duty to aid ! 90: individuals one at a time, such as by sending them individual messages, ! 91: and have no time to do this since we are busy doing things for the ! 92: entire community. If you want help for yourself in particular, you may ! 93: have to hire someone. The GNU project maintains a list of people ! 94: providing such services. It is distributed with GNU Emacs in file ! 95: ../etc/SERVICE, and can be requested from [email protected]. ! 96: ! 97: Anything addressed to the implementors and maintainers of a GNU program ! 98: via a bug-* list, should NOT be sent to the corresponding info-* list. ! 99: Bug reports reach the GNU maintainers quickest when they are sent to the ! 100: bug-* mailing list submittal address. Bug reports sent to the gnu.*.bug ! 101: newsgroups can be delayed several days. Bug reports sent to the comp.* ! 102: never make it to GNU maintainers - mail them directly! ! 103: ! 104: * [email protected] to subscribe to info-gnu ! 105: ** USENET newsgroup: gnu.announce ! 106: ** List submittal address: [email protected] ! 107: ! 108: This list distributes progress reports on the GNU Project, and asks ! 109: people for various kinds of help. It is NOT for general discussion. ! 110: ! 111: The list is filtered to remove items meant for info-gnu-request, that ! 112: can be answered by the moderator without bothering the list, or should ! 113: have been sent to another list. ! 114: ! 115: * [email protected] to subscribe to bug-gnu-emacs ! 116: ** USENET newsgroup: gnu.emacs.bug ! 117: ** Gnu Emacs bug reports to: [email protected] ! 118: ! 119: This list distributes bug reports, fixes for bugs, and suggestions for ! 120: improvements in GNU Emacs to the active maintainers of GNU Emacs. It is ! 121: the place to report GNU Emacs bugs by all users of GNU Emacs. ! 122: ! 123: Subscribers to bug-gnu-emacs automatically receive all info-gnu-emacs ! 124: messages. ! 125: ! 126: * [email protected] to subscribe to info-gnu-emacs ! 127: ** USENET newsgroup: gnu.emacs (and one-way into comp.emacs) ! 128: ** submittal address: [email protected] ! 129: ! 130: This list covers general questions and announcements about GNU Emacs. ! 131: Since it is a very large list, send it only those items that are ! 132: seriously important to many people. It is also gated one way to ! 133: USENET's newsgroup comp.emacs (once known as net.emacs). Do not report ! 134: GNU Emacs bugs to comp.emacs, instead mail them to ! 135: [email protected]. Users at non-USENET sites may receive ! 136: all articles from comp.emacs by making their request to: ! 137: [email protected] ! 138: ! 139: * [email protected] to subscribe to vms-gnu-emacs ! 140: ** USENET newsgroup: gnu.emacs.vms ! 141: ** submittal address: [email protected] ! 142: *** UUCP: ..!uunet!harvard!vms-gnu-emacs-request ! 143: ! 144: This list was a working group who did the initial port of GNU Emacs to ! 145: the VMS operating system. It still discusses problems and solutions to ! 146: the VMS port and the distribution of it. ! 147: ! 148: * [email protected] to subscribe to gnu-manual ! 149: ** USENET newsgroup: gnu.emacs.lisp.manual ! 150: ** submittal address: [email protected] ! 151: *** UUCP: ..!ihnp4!uiucdcs!gnu-manual-request ! 152: ! 153: This list is a working group whose volunteers write, proofread and ! 154: comment on the developing GNU Emacs Lisp programmers manual. ! 155: ! 156: * [email protected] to subscribe to bug-gdb ! 157: ** USENET newsgroup: gnu.gdb.bug ! 158: ** GDB bug reports to: [email protected] ! 159: ! 160: This list distributes bug reports, fixes for bugs, and suggestions for ! 161: improvements in GDB (Gnu's DeBugger) to the active maintainers of GDB. ! 162: It is the place to report GDB bugs by all users of GDB. ! 163: ! 164: Always report the version number gdb reports on startup, as well as the ! 165: operating system and hardware. ! 166: ! 167: There is neither a info-gdb list nor a gnu.gdb newsgroup at this time. ! 168: ! 169: * [email protected] to subscribe to bug-gcc ! 170: ** USENET newsgroup: gnu.gcc.bug ! 171: ** GCC bug reports to: [email protected] ! 172: ! 173: This list distributes bug reports, fixes for bugs, and suggestions for ! 174: improvements in the GNU C Compiler to its active developers. It is the ! 175: place to report GCC bugs by all testers of GCC. The GNU C Compiler ! 176: still has bugs in it, and is not quite ready for everyday use. ! 177: ! 178: Always report the version number of gcc, as well as the operating system ! 179: and hardware. ! 180: ! 181: Subscribers to bug-gcc automatically receive all info-gcc messages. ! 182: ! 183: * [email protected] to subscribe to info-gcc ! 184: ** USENET newsgroup: gnu.gcc ! 185: ** submittal address: [email protected] ! 186: ! 187: This list reports new releases and proven bug fixes to testers of the ! 188: GNU C Compiler. ! 189: ! 190: * [email protected] to subscribe to bug-g++ ! 191: ** USENET newsgroup: gnu.g++.bug ! 192: ** G++ and GDB+ bug reports: [email protected] ! 193: ! 194: This list distributes bug reports, fixes for bugs, and suggestions for ! 195: improvements in the GNU C++ Compiler and it's debugger GDB+ to their ! 196: active developers. It is the place to report G++ and GDB+ bugs by all ! 197: testers of G++ and GDB+. The GNU C++ Compiler is still in test release, ! 198: and is NOT ready for everyday use. ! 199: ! 200: Always report the version number of g++, as well as the operating system ! 201: and hardware. ! 202: ! 203: G++ uses the GNU C-Compiler back end. Active developers may wish to ! 204: subscribe to [email protected] as well. ! 205: ! 206: GDB+ uses much code from GDB. Active developers may wish to subscribe ! 207: to [email protected] as well. ! 208: ! 209: Subscribers to bug-g++ automatically receive all info-g++ messages. ! 210: ! 211: * [email protected] to subscribe to info-g++ ! 212: ** USENET newsgroup: gnu.g++ (and one-way into comp.lang.c++) ! 213: ** submittal address: [email protected] ! 214: ! 215: This list reports new releases, informations about ports and proven bug ! 216: fixes to testers of the GNU C++ Compiler. It is also gated one way to ! 217: USENET's newsgroup comp.lang.c++. Do not report g++ bugs to ! 218: comp.lang.c++, mail them to [email protected] instead. ! 219: ! 220: * [email protected] to subscribe to bug-lib-g++ ! 221: ** USENET newsgroup: gnu.g++.lib.bug ! 222: ** lib-g++ bug reports to: [email protected] ! 223: ! 224: This list distributes bug reports, fixes for bugs, and suggestions for ! 225: improvements in lib-g++ (Gnu's library for C++) to the active ! 226: maintainers of lib-g++. It is the place to report lib-g++ bugs by all ! 227: users of lib-g++. ! 228: ! 229: Always report the version number of lib-g++, as well as the operating ! 230: system and hardware. ! 231: ! 232: There is neither a info-lib-g++ list nor a gnu.g++.lib newsgroup at ! 233: this time. Announcements of new releases of lib-g++ are made on both ! 234: info-g++ and bug-lib-g++. ! 235: ! 236: * [email protected] to subscribe to bug-ghostscript ! 237: ** USENET newsgroup: gnu.ghostscript.bug ! 238: ** Ghostscript bug reports to: [email protected] ! 239: ! 240: This list distributes bug reports, fixes for bugs, and suggestions for ! 241: improvements in Ghostscript to the active maintainers of ghostscript. ! 242: It is the place to report bugs in Ghostscript by all users of ! 243: them. ! 244: ! 245: Always report the version number of the GNU program, as well as the ! 246: operating system and hardware. ! 247: ! 248: For now, new releases of Ghostscript will also be announced on this list. ! 249: ! 250: GhostScript is the GNU project implementation of a language and graphics ! 251: library with a remarkable similarity to PostScript(tm). ! 252: ! 253: There is neither a info-ghostscript list nor a gnu.ghostscript newsgroup ! 254: at this time. ! 255: ! 256: * [email protected] to subscribe to info-gnu-chess ! 257: ** USENET newsgroup: gnu.chess ! 258: ** submittal address: [email protected] ! 259: ! 260: This list reports new releases and information about the program GNU ! 261: Chess. ! 262: ! 263: * [email protected] to subscribe to bug-gnu-utils ! 264: ** USENET newsgroup: gnu.utils.bug ! 265: ** GNU Utilities bug reports to: [email protected] ! 266: ! 267: This list distributes bug reports, fixes for bugs, and suggestions for ! 268: improvements in GNU programs not covered by other bug-* mailing ! 269: lists/gnu.*.bug newsgroups to the active maintainers of these programs. ! 270: It is the place to report bugs in these GNU programs by all users of ! 271: them. ! 272: ! 273: Always report the version number of the GNU program, as well as the ! 274: operating system and hardware. ! 275: ! 276: There is neither a info-gnu-utils list nor a gnu.utils newsgroup at this ! 277: time. ! 278: ! 279: * info-gnus-request%[email protected] to subscribe ! 280: ** USENET newsgroup: NONE YET ! 281: ** Send contributions to: info-gnus%[email protected] ! 282: ! 283: The list is intended to exchange valuable information about GNUS, such ! 284: as bug reports, useful hooks, and extensions of GNUS. GNUS is an ! 285: NNTP-base network news reader for GNU Emacs (which also handles news ! 286: spools). English and Japanese are the official languages of the list. ! 287: ! 288: * [email protected] to subscribe ! 289: ** USENET newsgroup: gnu.emacs.gnus ! 290: ** Send contributions to: [email protected] ! 291: ! 292: The list has the same charter as info-gnus. The difference is that ! 293: English is the only official language of the list. ! 294: ! 295: info-gnu-english/comp.emacs.gnus is forward to info-gnus, but NOT ! 296: vice-versa. ! 297: ! 298: * [email protected] to subscribe to bug-gnu-emacs-ada ! 299: ** USENET newsgroup: NONE PLANNED ! 300: ** GNU-EMACS-ADA bug reports to: [email protected] ! 301: ! 302: This list distributes bug reports, fixes for bugs, and suggestions for ! 303: improvements in GNU Emacs' editing support of the Ada programming ! 304: language. ! 305: ! 306: Always report the version number, as well as the operating system ! 307: and hardware. ! 308: ! 309: There is neither a info-gnu-emacs-ada mailing list nor a newsgroup. ! 310: ! 311: Local variables: ! 312: mode: outline ! 313: fill-column: 72 ! 314: End:
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.