Mercurial > emacs
annotate etc/MAILINGLISTS @ 51270:827c306f0515
Add missing code from previous patch by David Ponce.
author | Juanma Barranquero <lekktu@gmail.com> |
---|---|
date | Tue, 27 May 2003 22:34:58 +0000 |
parents | 23a1cea22d13 |
children | 695cf19ef79e d7ddb3e565de |
rev | line source |
---|---|
26119 | 1 GNU Project Electronic Mailing Lists and gnUSENET Newsgroups |
2 Last Updated 1999-05-06 | |
3 | |
4 Please report improvements to: gnu@gnu.org | |
5 | |
6 * Mailing list archives | |
7 | |
8 The GNU mailing lists are archived at | |
9 ftp://ftp-mailing-list-archives.gnu.org/ | |
10 | |
11 * GNU mailing lists are also distributed as USENET news groups | |
12 | |
13 The mailing lists are gated both ways with the gnu.all newsgroups at | |
14 uunet. The one-to-one correspondence is indicated below. If | |
15 you don't know if your site is on USENET, ask your system administrator. | |
16 If you are a USENET site and don't get the gnu.all newsgroups, please | |
17 ask your USENET administrator to get them. If he has your feeds ask | |
18 their feeds, you should win. And everyone else wins: newsgroups make | |
19 better use of the limited bandwidth of the computer networks and your | |
20 home machine than mailing list traffic; and staying off the mailing | |
21 lists make better use of the people who maintain the lists and the | |
22 machines that the GNU people working with rms use (i.e. we have more | |
23 time to produce code!!). Thanx. | |
24 | |
25 * Getting the mailing lists directly | |
26 | |
27 If several users at your site or local network want to read a list and | |
28 you aren't a USENET site, Project GNU would prefer that you would set up | |
29 one address that redistributes locally. This reduces overhead on our | |
30 people and machines, your gateway machine, and the network(s) used to | |
31 transport the mail from us to you. | |
32 | |
33 * How to subscribe to and report bugs in mailing lists | |
34 | |
35 Send requests to be added or removed, to help-gnu-emacs-request (or | |
36 info-gnu-request, bug-gdb-request, etc.), NOT to info-gnu-emacs (or | |
37 info-gnu, etc.). Most <LIST_NAME>-request addresses are now handled | |
38 automagically by the SmartList program. | |
39 | |
40 If you need to report problems to a human, send mail to gnu@gnu.org | |
41 explaining the problem. | |
42 | |
43 Many of the GNU mailing lists are very large and are received by many | |
44 people. Please don't send them anything that is not seriously important | |
45 to all their readers. All GNU mailing lists are unmoderated mail | |
46 reflectors, except info-gnu, info-gnu-emacs, info-gcc, info-g++, | |
47 info-gnu-fortran. | |
48 | |
49 All addresses below are in internet format. Consult the mail guru for | |
50 your computer to figure out address syntaxes from other networks. From | |
51 UUCP machines: | |
52 ..!ucbvax!gnu.org!ADDRESS | |
53 ..!uunet!gnu.org!ADDRESS | |
54 | |
55 If a message you mail to a list is returned from a MAILER-DAEMON (often | |
56 with the line: | |
57 ----- Transcript of session follows ----- | |
58 don't resend the message to the list. All this return means is that | |
59 your original message failed to reach a few addresses on the list. Such | |
60 messages are NEVER a reason to resend a piece of mail a 2nd time. This | |
61 just bothers all (less the few delivery failures (which will probably | |
62 just fail again!)) of the readers of the list with a message they have | |
63 already seen. It also wastes computer and network resources. | |
64 | |
65 It is appropriate to send these to the -request address for a list, and | |
66 ask them to check the problem out. | |
67 | |
68 * Send Specific Requests for Information to: gnu@gnu.org | |
69 | |
70 Specific requests for information about obtaining GNU software, or GNU | |
71 activities in Cambridge and elsewhere can be directed to: | |
72 gnu@gnu.org | |
73 | |
74 * General Information about all lists | |
75 | |
76 Please keep each message under 25,000 characters. Some mailers bounce | |
77 messages that are longer than this. If your message is long, it is | |
78 generally better to send a message offering to make the large file | |
79 available to only those people who want it (e.g. mailing it to people | |
80 who ask, or putting it up for FTP). In the case of gnu.emacs.sources, | |
81 somewhat larger postings (up to 10 parts of no more than 25,000 | |
82 characters each) are acceptable (assuming they are likely to be of | |
83 interest to a reasonable number of people); if it is larger than that | |
84 have it added to archive.cis.ohio-state.edu (the GNU Emacs Lisp ftp and | |
85 uucp archive) and announce its location there. Good bug reports are | |
86 short. See section '* General Information about bug-* lists and ...' | |
87 for further details. | |
88 | |
89 Most of the time, when you reply to a message sent to a list, the reply | |
90 should not go to the list. But most mail reading programs supply, by | |
91 default, all the recipients of the original as recipients of the reply. | |
92 Make a point of deleting the list address from the header when it does | |
93 not belong. This prevents bothering all readers of a list, and reduces | |
94 network congestion. | |
95 | |
96 The GNU mailing lists and newsgroups, like the GNU project itself, exist | |
97 to promote the freedom to share software. So don't use these lists to | |
98 promote or recommend non-free software or documentation, like | |
99 proprietary books on GNU software. (Using them to post ordering | |
100 information is the ultimate faux pas.) If there is no free program to | |
101 do a certain task, then somebody should write one! Similarly, free | |
102 documentation that is inadequate should be improved--a way in which | |
103 non-programmers can make a valuable contribution. See also the article | |
104 at <URL:http://www.gnu.org/philosophy/free-doc.html>. | |
105 | |
106 * General Information about info-* lists | |
107 | |
108 These lists and their newsgroups are meant for important announcements. | |
109 Since the GNU project uses software development as a means for social | |
110 change, the announcements may be technical or political. | |
111 | |
112 Most GNU projects info-* lists (and their corresponding gnu.*.announce | |
113 newsgroups) are moderated to keep their content significant and | |
114 relevant. If you have a bug to report, send it to the bug-* list. If | |
115 you need help on something else and the help-* list exists, ask it. | |
116 | |
117 See section '* General Information about all lists'. | |
118 | |
119 * General Information about help-* lists | |
120 | |
121 These lists (and their newsgroups) exist for anyone to ask questions | |
122 about the GNU software that the list deals with. The lists are read by | |
123 people who are willing to take the time to help other users. | |
124 | |
125 When you answer the questions that people ask on the help-* lists, keep | |
126 in mind that you shouldn't answer by promoting a proprietary program as | |
127 a solution. The only real solutions are the ones all the readers can | |
128 share. | |
129 | |
130 If a program crashes, or if you build it following the standard | |
131 procedure on a system on which it is supposed to work and it does not | |
132 work at all, or if an command does not behave as it is documented to | |
133 behave, this is a bug. Don't send bug reports to a help-* list; mail | |
134 them to the bug-* list instead. | |
135 | |
136 See section '* General Information about all lists'. | |
137 | |
138 * General Information about bug-* lists and reporting program bugs | |
139 | |
140 If you think something is a bug in a program, it might be one; or, it | |
141 might be a misunderstanding or even a feature. Before beginning to | |
142 report bugs, please read the section ``Reporting Emacs Bugs'' toward the | |
143 end of the GNU Emacs reference manual (or node Emacs/Bugs in Emacs's | |
144 built-in Info system) for a discussion of how and when to send in bug | |
145 reports. For GNU programs other than GNU Emacs, also consult their | |
146 documentation for their bug reporting procedures. Always include the | |
147 version number of the GNU program, as well as the operating system and | |
148 machine the program was ran on (if the program doesn't have a version | |
149 number, send the date of the latest entry in the file ChangeLog). For | |
150 GNU Emacs bugs, type "M-x emacs-version". A debugger backtrace of any | |
151 core dump can also be useful. Be careful to separate out hypothesis | |
152 from fact! For bugs in GNU Emacs lisp, set variable debug-on-error to | |
153 t, and re-enter the command(s) that cause the error message; Emacs will | |
154 pop up a debug buffer if something is wrong; please include a copy of | |
155 the buffer in your bug report. Please also try to make your bug report | |
156 as short as possible; distill the problem to as few lines of code and/or | |
157 input as possible. GNU maintainers give priority to the shortest, high | |
158 quality bug reports. | |
159 | |
160 Please don't send in a patch without a test case to illustrate the | |
161 problem the patch is supposed to fix. Sometimes the patches aren't | |
162 correct or aren't the best way to do the job, and without a test case | |
163 there is no way to debug an alternate fix. | |
164 | |
165 The purpose of reporting a bug is to enable the bug to be fixed for the | |
166 sake of the whole community of users. You may or may not receive a | |
167 response; the maintainers will send one if that helps them find or | |
168 verify a fix. Most GNU maintainers are volunteers and all are | |
169 overworked; they don't have time to help individuals and still fix the | |
170 bugs and make the improvements that everyone wants. If you want help | |
171 for yourself in particular, you may have to hire someone. The GNU | |
172 project maintains a list of people providing such services. It is | |
173 distributed with GNU Emacs in file etc/SERVICE, and can be requested | |
174 from gnu@gnu.org. | |
175 | |
176 Anything addressed to the implementors and maintainers of a GNU program | |
177 via a bug-* list, should NOT be sent to the corresponding info-* or | |
178 help-* list. | |
179 | |
180 Please DON'T post your bug reports on the gnu.*.bug newsgroups! Mail | |
181 them to bug-*@gnu.org instead! At first sight, it seems to make no | |
182 difference: anything sent to one will be propagated to the other; but: | |
183 - if you post on the newsgroup, the information about how to | |
184 reach you is lost in the message that goes on the mailing list. It | |
185 can be very important to know how to reach you, if there is anything | |
186 in the bug report that we don't understand; | |
187 - bug reports reach the GNU maintainers quickest when they are | |
188 sent to the bug-* mailing list submittal address; | |
189 - mail is much more reliable then netnews; and | |
190 - if the internet mailers can't get your bug report delivered, | |
191 they almost always send you an error message, so you can find another | |
192 way to get the bug report in. When netnews fails to get your message | |
193 delivered to the maintainers, you'll never know about it and the | |
194 maintainers will never see the bug report. | |
195 | |
196 And please DON'T post your GNU bug reports to comp.* or other gnu.* | |
197 newsgroups, they never make it to the GNU maintainers at all. Please | |
198 mail them to bug-*@gnu.org instead! | |
199 | |
200 See section '* General Information about all lists'. | |
201 | |
202 * info-gnu-request@gnu.org to subscribe to info-gnu | |
203 ** gnUSENET newsgroup: gnu.announce | |
204 ** Send announcements to: info-gnu@gnu.org | |
205 | |
206 This list distributes progress reports on the GNU Project. It is also | |
207 used by the GNU Project to ask people for various kinds of help. It is | |
208 NOT for general discussion. | |
209 | |
210 The list is filtered to remove items meant for info-gnu-request, that | |
211 can be answered by the moderator without bothering the list, or should | |
212 have been sent to another list. | |
213 | |
214 See section '* General Information about info-* lists'. | |
215 | |
216 * gnu-misc-discuss-request@gnu.org to subscribe to gnu-misc-discuss | |
217 ** gnUSENET newsgroup: gnu.misc.discuss | |
218 ** Send contributions to: gnu-misc-discuss@gnu.org | |
219 | |
220 This list is for serious discussion of freed software, the GNU Project, | |
221 the GNU Manifesto, and their implications. It's THE place for | |
222 discussion that is not appropriate in the other GNU mailing lists and | |
223 gnUSENET newsgroups. | |
224 | |
225 Flaming is out of place. Tit-for-tat is not welcome. Repetition | |
226 should not occur. | |
227 | |
228 Good READING and writing are expected. Before posting, wait a while, | |
229 cool off, and think. | |
230 | |
231 Don't use this group for complaints and bug reports about GNU software! | |
232 The maintainers don't read this group; they won't see your complaint. | |
233 Use the appropriate bug-reporting mailing list instead, so that people | |
234 who can do something about the problem will see it. | |
235 | |
236 Don't trust pronouncements made on gnu-misc-discuss about what GNU is, | |
237 what FSF position is, what the GNU General Public License is, etc., | |
238 unless they are made by someone you know is well connected with GNU and | |
239 are sure the message is not forged. | |
240 | |
241 USENET and gnUSENET readers are expected to have read ALL the articles | |
242 in news.announce.newusers before posting. If news.announce.newusers is | |
243 empty at your site, wait (the articles are posted monthly), your posting | |
244 isn't that urgent! Readers on the Internet can anonymous FTP these | |
245 articles from host ftp.uu.net under directory ?? | |
246 | |
247 Someone from the Free Software Foundation will attempt to follow this | |
248 group as time and volume permits. | |
249 | |
250 Remember, "GNUs Not Unix" and "gnUSENET is Not USENET". We have | |
251 higher standards! | |
252 | |
253 Note that sending technical questions about specific GNU software to | |
254 gnu-misc-discuss is likely to be less useful than sending them to the | |
255 appropriate mailing list or gnUSENET newsgroup, since more technical | |
256 people read those. | |
257 | |
258 * bug-gnu-sql-request@gnu.org to subscribe to bug-gnu-sql | |
259 ** gnUSENET newsgroup: NONE PLANNED | |
260 ** GNU-SQL BUG reports to: bug-gnu-sql@gnu.org | |
261 | |
262 This list distributes, to the active maintainers of GNU's SQL (GNU's SQL | |
263 full scale database server), bug reports and fixes for, and suggestions | |
264 for improvements to GNU's SQL. User discussion of GNU's SQL also occurs | |
265 here. | |
266 | |
267 There are no other GNU mailing lists or gnUSENET newsgroups for GNU's SQL. | |
268 | |
269 See section '* General Information about bug-* lists and reporting | |
270 program bugs'. | |
271 | |
272 * bug-guile-request@gnu.org to subscribe to bug-guile | |
273 ** gnUSENET newsgroup: NONE PLANNED | |
274 ** GUILE BUG reports to: bug-guile@gnu.org | |
275 | |
276 This list distributes, to the active maintainers of GUILE (GNU's | |
277 Ubiquitous Extension Language), bug reports and fixes for, and suggestions for | |
278 improvements to GUILE. User discussion of GUILE also occurs here. | |
279 | |
280 There are no other GNU mailing lists or gnUSENET newsgroups for GUILE . | |
281 | |
282 See section '* General Information about bug-* lists and reporting | |
283 program bugs'. | |
284 | |
285 * guile-sources-request@gnu.org to subscribe to guile-sources | |
286 ** gnUSENET newsgroup: NONE PLANNED | |
287 ** Guile source code to: guile-sources@gnu.org | |
288 | |
289 This list will be for the posting, by their authors, of GUILE, Scheme, | |
290 and C sources and patches that improve Guile. Its contents will be | |
291 reviewed by the FSF for inclusion in future releases of GUILE. | |
292 | |
293 Please do NOT discuss or request source code here. Use bug-guile for | |
294 those purposes. This allows the automatic archiving of sources posted | |
295 to this list. | |
296 | |
297 Please do NOT post such sources to any other GNU mailing list (e.g | |
298 bug-guile) or gnUSENET newsgroups. It's up to each poster to decide | |
299 whether to cross-post to any non-gnUSENET newsgroup. | |
300 | |
301 Please do NOT announce that you have posted source code to guile.sources | |
302 to any other GNU mailing list (e.g. bug-guile) or gnUSENET newsgroups. | |
303 People who want to keep up with sources will read this list. It's up to | |
304 each poster to decide whether to announce a guile.sources article in any | |
305 non-gnUSENET newsgroup (e.g. comp.emacs or comp.sources.d). | |
306 | |
307 If source or patches that were previously posted or a simple fix is | |
308 requested in bug-guile, please mail it to the requester. Do NOT | |
309 repost it. If you also want something that is requested, send mail to | |
310 the requester asking him to forward it to you. This kind of traffic is | |
311 best handled by e-mail, not by a broadcast medium that reaches millions | |
312 of sites. | |
313 | |
314 If the requested source is very long (>10k bytes) send mail offering to | |
315 send it. This prevents the requester from getting many redundant copies | |
316 and saves network bandwidth. | |
317 | |
318 * bug-gnustep-request@gnu.org to subscribe to bug-gnustep | |
319 ** gnUSENET newsgroup: gnu.gnustep.bug | |
320 ** Gnustep bug reports to: bug-gnustep@gnu.org | |
321 ** FAQ-URL: none known | |
322 ** FAQ-Archive-name: none known | |
323 ** FAQ-Posting-frequency: none known | |
324 | |
325 This list distributes bug reports for, fixes for bugs in, and | |
326 suggestions for improvements in GNUstep to its active developers. | |
327 | |
328 Subscribers to bug-gnustep get all info-gnustep messages. | |
329 | |
330 See section '* General Information about bug-* lists and reporting | |
331 program bugs'. | |
332 | |
333 * help-gnustep-request@gnu.org to subscribe to help-gnustep | |
49600
23a1cea22d13
Trailing whitespace deleted.
Juanma Barranquero <lekktu@gmail.com>
parents:
48786
diff
changeset
|
334 ** gnUSENET newsgroup: gnu.gnustep.help |
26119 | 335 ** Send contributions to: help-gnustep@gnu.org |
336 ** FAQ-URL: none known | |
337 ** FAQ-Archive-name: none known | |
338 ** FAQ-Posting-frequency: none known | |
339 | |
340 This list is the place for users and installers of the GNUstep to ask | |
341 for help. Please send bug reports to bug-gnustep@gnu.org | |
342 instead of posting them here. | |
343 | |
344 See section '* General Information about help-* lists'. | |
345 | |
346 * discuss-gnustep-request@gnu.org to subscribe to discuss-gnustep | |
49600
23a1cea22d13
Trailing whitespace deleted.
Juanma Barranquero <lekktu@gmail.com>
parents:
48786
diff
changeset
|
347 ** gnUSENET newsgroup: gnu.gnustep.discuss |
26119 | 348 ** Send contributions to: discuss-gnustep@gnu.org |
349 ** FAQ-URL: none known | |
350 ** FAQ-Archive-name: none known | |
351 ** FAQ-Posting-frequency: none known | |
352 | |
353 This list is the place for GNUstep users and developers to discuss | |
354 GNUstep. Please send bug reports to bug-gnustep@gnu.org | |
355 instead of posting them here. | |
356 | |
357 See section '* General Information about discuss-* lists'. | |
358 | |
359 * info-gnustep-request@gnu.org to subscribe to info-gnustep | |
360 ** gnUSENET newsgroup: gnu.gnustep.announce | |
361 ** Send announcements to: info-gnustep@gnu.org | |
362 ** FAQ-URL: none known | |
363 ** FAQ-Archive-name: none known | |
364 ** FAQ-Posting-frequency: none known | |
365 | |
366 This list distributes announcements and progress reports on GNUstep. | |
367 It is NOT for general discussion; please use discuss-gnustep for that. | |
368 | |
369 The list is filtered to remove items meant for info-gnustep-request, that | |
370 can be answered by the moderator without bothering the list, or should | |
371 have been sent to another list. | |
372 | |
373 Do not report GNUstep bugs to info-gnustep, help-gnustep, or | |
374 discuss-gnustep, mail them to bug-gnustep@gnu.org instead. | |
375 | |
376 See section '* General Information about info-* lists'. | |
377 | |
378 * bug-hurd-request@gnu.org to subscribe to bug-hurd | |
379 ** gnUSENET newsgroup: NONE | |
380 ** Hurd bug reports to: bug-hurd@gnu.org | |
381 | |
382 This list distributes bug reports for, fixes for bugs in, and | |
383 suggestions for improvements in the GNU Hurd to its active developers. | |
384 | |
385 No info-gnu-hurd list is planned. Announcements about the GNU Hurd will | |
386 be made to the list info-gnu@gnu.org (see above). | |
387 | |
388 See section '* General Information about bug-* lists and reporting | |
389 program bugs'. | |
390 | |
391 * help-hurd-request@gnu.org to subscribe to help-hurd | |
392 ** gnUSENET newsgroup: NONE | |
393 ** Send contributions to: help-hurd@gnu.org | |
394 | |
395 This list is the place for users and installers of the GNU Hurd to ask | |
396 for help. | |
397 | |
398 No info-gnu-hurd list is planned. Announcements about the GNU Hurd will | |
399 be made to the list info-gnu@gnu.org (see above). | |
400 | |
401 See section '* General Information about help-* lists'. | |
402 | |
403 * hurd-ann-request@gnu.org IS NOW DEFUNCT | |
404 ** gnUSENET newsgroup: NEVER EXISTED | |
405 ** DEAD address: hurd-ann@gnu.org | |
406 | |
407 This list is dead. Announcements about the GNU Hurd will be made to the | |
408 list info-gnu@gnu.org (see above). | |
409 | |
410 * discuss-gnu-electric-request@gnu.org to subscribe to discuss-gnu-electric | |
411 ** gnUSENET newsgroup: NONE | |
412 ** Send contributions to: discuss-gnu-electric@gnu.org | |
413 | |
49600
23a1cea22d13
Trailing whitespace deleted.
Juanma Barranquero <lekktu@gmail.com>
parents:
48786
diff
changeset
|
414 This list is the place for user discussion of Gnu Electric, a |
26119 | 415 sophisticated electrical CAD system that can handle many forms of |
416 circuit design. Please send bug reports to bug-gnu-electric@gnu.org | |
417 (see next entry). | |
418 | |
419 * bug-gnu-electric-request@gnu.org to subscribe to bug-gnu-electric | |
420 ** gnUSENET newsgroup: NONE | |
421 ** Gnu Electric bug reports to: bug-gnu-electric@gnu.org | |
422 | |
423 This list distributes, to the active maintainers of GNU Electric, bug | |
424 reports and fixes for, and suggestions for improvements in GNU Electric, | |
425 a sophisticated electrical CAD system that can handle many forms of | |
426 circuit design. | |
427 | |
428 No info-gnu-electric list exists; announcements of new releases are | |
429 made to info-gnu@gnu.org (see above). | |
430 | |
431 See section '* General Information about bug-* lists and reporting | |
432 program bugs'. | |
433 | |
434 * bug-gnu-emacs-request@gnu.org to subscribe to bug-gnu-emacs | |
435 ** gnUSENET newsgroup: gnu.emacs.bug | |
436 ** Gnu Emacs bug reports to: bug-gnu-emacs@gnu.org | |
437 | |
438 This list distributes, to the active maintainers of GNU Emacs, bug | |
439 reports and fixes for, and suggestions for improvements in GNU Emacs. | |
440 | |
441 Send bugs in the GNU Emacs Lisp reference manual to: | |
442 lisp-manual-bugs@gnu.org | |
443 | |
444 lisp-manual-bugs is neither a mailing list nor a gnUSENET newsgroup. | |
445 It's just a bug-reporting address. | |
446 | |
447 Subscribers to bug-gnu-emacs get all info-gnu-emacs messages. | |
448 | |
449 See section '* General Information about bug-* lists and reporting | |
450 program bugs'. | |
451 | |
452 * gnu-emacs-sources-request@gnu.org to subscribe to gnu-emacs-sources | |
453 ** gnUSENET newsgroup: gnu.emacs.sources | |
454 ** Gnu Emacs source code to: gnu-emacs-sources@gnu.org | |
455 | |
456 This list/newsgroup will be for the posting, by their authors, of Emacs | |
457 Lisp and C sources and patches that improve GNU Emacs. Its contents | |
458 will be reviewed by the FSF for inclusion in future releases of GNU | |
459 Emacs. | |
460 | |
461 Please do NOT discuss or request source code here. Use | |
462 help-gnu-emacs/gnu.emacs.help for those purposes. This allows the | |
463 automatic archiving of sources posted to this list/newsgroup. | |
464 | |
465 Please do NOT post such sources to any other GNU mailing list (e.g | |
466 help-gnu-emacs) or gnUSENET newsgroups (e.g. gnu.emacs.help). It's up | |
467 to each poster to decide whether to cross-post to any non-gnUSENET | |
468 newsgroup (e.g. comp.emacs or vmsnet.sources). | |
469 | |
470 Please do NOT announce that you have posted source code to | |
471 gnu.emacs.sources to any other GNU mailing list (e.g. help-gnu-emacs) or | |
472 gnUSENET newsgroups (e.g. gnu.emacs.help). People who want to keep up | |
473 with sources will read this list/newsgroup. It's up to each poster to | |
474 decide whether to announce a gnu.emacs.sources article in any | |
475 non-gnUSENET newsgroup (e.g. comp.emacs or comp.sources.d). | |
476 | |
477 If source or patches that were previously posted or a simple fix is | |
478 requested in help-gnu-emacs, please mail it to the requester. Do NOT | |
479 repost it. If you also want something that is requested, send mail to | |
480 the requester asking him to forward it to you. This kind of traffic is | |
481 best handled by e-mail, not by a broadcast medium that reaches millions | |
482 of sites. | |
483 | |
484 If the requested source is very long (>10k bytes) send mail offering to | |
485 send it. This prevents the requester from getting many redundant copies | |
486 and saves network bandwidth. | |
487 | |
488 * help-gnu-emacs-request@gnu.org to subscribe to help-gnu-emacs | |
489 ** gnUSENET newsgroup: gnu.emacs.help (and one-way into comp.emacs) | |
490 ** Send contributions to: help-gnu-emacs@gnu.org | |
491 | |
492 This list is the place for users and installers of GNU Emacs to ask for | |
493 help. Please send bug reports to bug-gnu-emacs instead of posting them | |
494 here. | |
495 | |
496 Since help-gnu-emacs is a very large list, send it only those items that | |
497 are seriously important to many people. | |
498 | |
499 If source or patches that were previously posted or a simple fix is | |
500 requested in help-gnu-emacs, please mail it to the requester. Do NOT | |
501 repost it. If you also want something that is requested, send mail to | |
502 the requester asking him to forward it to you. This kind of traffic is | |
503 best handled by e-mail, not a broadcast medium that reaches millions of | |
504 sites. | |
505 | |
506 This list is also gated one way to USENET's newsgroup comp.emacs (once | |
507 known as net.emacs). This one-way gating is done for users whose sites | |
508 get comp.emacs, but not gnu.emacs.help. Users at non-USENET sites may | |
509 receive all articles from comp.emacs by making their request to: | |
510 unix-emacs-request@bbn.com | |
511 | |
512 If Emacs crashes, or if you build Emacs following the standard procedure | |
513 on a system which Emacs is supposed to work on (see etc/MACHINES) and it | |
514 does not work at all, or if an editing command does not behave as it is | |
515 documented to behave, this is a bug. Don't send bug reports to | |
516 help-gnu-emacs (gnu.emacs.help) or post them to comp.emacs; mail them to | |
517 bug-gnu-emacs@gnu.org instead. | |
518 | |
519 See section '* General Information about help-* lists'. | |
520 | |
521 * info-gnu-emacs-request@gnu.org to subscribe to info-gnu-emacs | |
522 ** gnUSENET newsgroup: gnu.emacs.announce (and one-way into comp.emacs) | |
523 ** Send announcements to: info-gnu-emacs@gnu.org | |
524 | |
525 This list distributes announcements and progress reports on GNU Emacs. | |
526 It is NOT for general discussion; please use help-gnu-emacs for that. | |
527 | |
528 The list is filtered to remove items meant for info-gnu-emacs-request, | |
529 that can be answered by the moderator without bothering the list, or | |
530 should have been sent to another list. | |
531 | |
532 info-gnu-emacs is also gated one way to USENET's newsgroup comp.emacs | |
533 (once known as net.emacs). This one-way gating is done for users whose | |
534 sites get comp.emacs, but not gnu.emacs.announce. Users at non-USENET | |
535 sites may receive all articles from comp.emacs by making their request | |
536 to: unix-emacs-request@bbn.com | |
537 | |
538 Do not report GNU Emacs bugs to info-gnu-emacs or comp.emacs, instead | |
539 mail them to bug-gnu-emacs@gnu.org. | |
540 | |
541 See section '* General Information about info-* lists'. | |
542 | |
543 * vms-gnu-emacs-request@gnu.org to subscribe | |
544 ** gnUSENET newsgroup: gnu.emacs.vms | |
545 ** Send contributions to: vms-gnu-emacs@gnu.org | |
546 | |
547 This list was a working group who did the initial port of GNU Emacs to | |
548 the VMS operating system. It still discusses problems and solutions to | |
549 the VMS port and the distribution of it. | |
550 | |
551 * bug-bash-request@gnu.org to subscribe to bug-bash | |
552 ** gnUSENET newsgroup: gnu.bash.bug | |
553 ** BASH bug reports to: bug-bash@gnu.org | |
554 | |
555 This list distributes, to the active maintainers of BASH (the Bourne | |
556 Again SHell), bug reports and fixes for, and suggestions for | |
557 improvements in BASH. User discussion of BASH also occurs here. | |
558 | |
559 Always report the version number of the operating system, hardware, and | |
560 bash (flag -version on startup or check the variable $BASH_VERSION in a | |
561 running bash). | |
562 | |
563 There are no other GNU mailing lists or gnUSENET newsgroups for BASH. | |
564 | |
565 See section '* General Information about bug-* lists and reporting | |
566 program bugs'. | |
567 | |
568 * bug-gdb-request@gnu.org to subscribe to bug-gdb | |
569 ** gnUSENET newsgroup: gnu.gdb.bug | |
570 ** GDB bug reports to: bug-gdb@gnu.org | |
571 | |
572 This list distributes, to the active maintainers of GDB (Gnu's | |
573 DeBugger), bug reports and fixes for, and suggestions for improvements | |
574 in GDB. This list is also for user discussion. | |
575 | |
576 There are no other GNU mailing lists or gnUSENET newsgroups for GDB. | |
577 | |
578 See section '* General Information about bug-* lists and reporting | |
579 program bugs'. | |
580 | |
581 * bug-ncurses-request@gnu.org to subscribe to bug-ncurses | |
582 ** gnUSENET newsgroup: none | |
583 ** NCURSES bug reports to: bug-ncurses@gnu.org | |
584 | |
585 This list distributes, to the active maintainers of ncurses | |
49600
23a1cea22d13
Trailing whitespace deleted.
Juanma Barranquero <lekktu@gmail.com>
parents:
48786
diff
changeset
|
586 (a free implementation of the Unix curses API) bug reports and fixes |
26119 | 587 for, and suggestions for improvements in ncurses. Users can also |
588 subscribe to this list. | |
589 | |
590 See section '* General Information about bug-* lists and reporting | |
591 program bugs'. | |
592 | |
593 * help-ncurses-request@gnu.org to subscribe to help-ncurses | |
594 ** gnUSENET newsgroup: none | |
595 ** posts go to: help-ncurses@gnu.org | |
596 | |
597 This list is the place for users and installers of ncurses to ask for | |
598 help. Please send bug reports to bug-ncurses instead of posting them | |
599 here. | |
600 | |
601 See section '* General Information about help-* lists' | |
602 | |
603 * bug-gnats-request@gnu.org to subscribe to bug-gnats | |
604 ** gnUSENET newsgroup: None | |
605 ** GNATS bug reports to: bug-gnats@gnu.org | |
606 | |
607 This list distributes, to the active maintainers of GNATS (GNats: A | |
608 Tracking System), bug reports and fixes for, and suggestions for improvements | |
609 in GNATS. This list is also for user discussion. | |
610 | |
611 There are no other GNU mailing lists or gnUSENET newsgroups for GNATS. | |
612 | |
613 See section '* General Information about bug-* lists and reporting | |
614 program bugs'. | |
615 | |
616 * bug-octave-request@bevo.che.utexas.edu to subscribe to bug-octave | |
617 ** gnUSENET newsgroup: NONE PLANNED | |
618 ** Octave bug reports to: bug-octave@bevo.che.utexas.edu | |
619 | |
620 This list distributes, to the active maintainers of Octave (a system | |
621 for numerical computations), bug reports and fixes for, and | |
622 suggestions for improvements to Octave. | |
623 | |
624 The help-octave mailing list is for user discussion of Octave. | |
625 | |
626 See section '* General Information about bug-* lists and reporting | |
627 program bugs'. | |
628 | |
629 | |
630 * help-octave-request@bevo.che.utexas.edu to subscribe to help-octave | |
631 ** gnUSENET newsgroup: NONE PLANNED | |
632 ** Send contributions to: help-octave@bevo.che.utexas.edu | |
633 | |
634 This list is the place for users and installers of Octave to ask for | |
635 help. Please send bug reports to bug-octave instead of posting them | |
636 here. | |
637 | |
638 If Octave crashes, or if you build Octave following the standard | |
639 procedure on a system on which Octave is supposed to work on and it | |
640 does not work at all, or if a command does not behave as it is | |
641 documented to behave, this is a bug. Don't send bug reports to | |
642 help-octave; mail them to bug-octave@che.utexas.edu instead. | |
643 | |
644 See section '* General Information about help-* lists'. | |
645 | |
646 * bug-bison-request@gnu.org to subscribe to bug-bison | |
647 ** gnUSENET newsgroup: NONE | |
648 ** Bison bug reports to: bug-bison@gnu.org | |
649 | |
650 This list distributes, to the active maintainers of Bison | |
651 bug reports and fixes for, and suggestions for improvements | |
652 in Bison. User discussion of Bison bugs occurs here. | |
653 | |
654 See section '* General Information about bug-* lists and reporting | |
655 program bugs'. | |
656 | |
657 * help-bison-request@gnu.org to subscribe to help-bison | |
658 ** gnUSENET newsgroup: NONE | |
659 ** Send contributions to: help-bison@gnu.org | |
660 | |
661 This list is the place for users and installers of Bison | |
662 to ask for help. Please send bug reports to bug-bison instead | |
663 of posting them here. | |
664 | |
665 See section '* General Information about help-* lists'. | |
666 | |
667 * bug-make-request@gnu.org to subscribe to bug-make | |
668 ** gnUSENET newsgroup: NONE | |
669 ** Make bug reports to: bug-make@gnu.org | |
670 | |
671 This list distributes, to the active maintainers of GNU make | |
672 bug reports and fixes for, and suggestions for improvements | |
673 in GNU make. User discussion of GNU make bugs occurs here. | |
674 | |
675 See section '* General Information about bug-* lists and reporting | |
676 program bugs'. | |
677 | |
678 * help-make-request@gnu.org to subscribe to help-make | |
679 ** gnUSENET newsgroup: NONE | |
680 ** Send contributions to: help-make@gnu.org | |
681 | |
682 This list is the place for users and installers of GNU make | |
683 to ask for help. Please send bug reports to bug-make instead | |
684 of posting them here. | |
685 | |
686 See section '* General Information about help-* lists'. | |
687 | |
688 * help-flex-request@gnu.org to subscribe to help-flex | |
689 ** gnUSENET newsgroup: NONE | |
690 ** Send contributions to: help-flex@gnu.org | |
691 | |
692 This list is the place for users and installers of Flex | |
693 to ask for help. Please send bug reports to bug-gnu-utils instead | |
694 of posting them here. | |
695 | |
696 See section '* General Information about help-* lists'. | |
697 | |
698 * bug-rcs-request@gnu.org to subscribe to bug-rcs | |
699 ** gnUSENET newsgroup: NONE | |
700 ** RCS bug reports to: bug-rcs@gnu.org | |
701 | |
702 This list distributes, to the active maintainers of RCS | |
703 bug reports and fixes for, and suggestions for improvements | |
704 in RCS. User discussion of RCS bugs occurs here. | |
705 | |
706 See section '* General Information about bug-* lists and reporting | |
707 program bugs'. | |
708 | |
709 * help-rcs-request@gnu.org to subscribe to help-rcs | |
710 ** gnUSENET newsgroup: NONE | |
711 ** Send contributions to: help-rcs@gnu.org | |
712 | |
713 This list is the place for users and installers of RCS | |
714 to ask for help. Please send bug reports to bug-rcs instead | |
715 of posting them here. | |
716 | |
717 See section '* General Information about help-* lists'. | |
718 | |
719 * bug-gcc-request@gnu.org to subscribe to bug-gcc | |
720 ** gnUSENET newsgroup: gnu.gcc.bug | |
721 ** GCC bug reports to: bug-gcc@gnu.org | |
722 | |
723 This list distributes bug reports for, fixes for bugs in, and | |
724 suggestions for improvements in the GNU C Compiler to its active | |
725 developers. | |
726 | |
727 Please don't send in a patch without a test case to illustrate the | |
728 problem the patch is supposed to fix. Sometimes the patches aren't | |
729 correct or aren't the best way to do the job, and without a test case | |
730 there is no way to debug an alternate fix. | |
731 | |
732 The most convenient form of test case is a piece of cpp output that can | |
733 be passed directly to cc1. Preferably written in C, not C++ or | |
734 Objective C. | |
735 | |
736 Subscribers to bug-gcc get all info-gcc messages. | |
737 | |
738 See section '* General Information about bug-* lists and reporting | |
739 program bugs'. | |
740 | |
741 * help-gcc-request@gnu.org to subscribe to help-gcc | |
742 ** gnUSENET newsgroup: gnu.gcc.help | |
743 ** Send contributions to: help-gcc@gnu.org | |
744 | |
745 This list is the place for users and installers of the GNU C Compiler to | |
746 ask for help. | |
747 | |
748 If gcc crashes, or if you build gcc following the standard procedure on | |
749 a system which gcc is supposed to work on (see config.sub) and it does | |
750 not work at all, or if an command line option does not behave as it is | |
751 documented to behave, this is a bug. Don't send bug reports to help-gcc | |
752 (gnu.gcc.help); mail them to bug-gcc@gnu.org instead. | |
753 | |
754 See section '* General Information about help-* lists'. | |
755 | |
756 * info-gcc-request@gnu.org to subscribe to info-gcc | |
757 ** gnUSENET newsgroup: gnu.gcc.announce | |
758 ** Send announcements to: info-gcc@gnu.org | |
759 | |
760 This list distributes announcements and progress reports on the GNU C | |
761 Compiler. It is NOT for general discussion; please use help-gcc for | |
762 that. | |
763 | |
764 The list is filtered to remove items meant for info-gcc-request, that | |
765 can be answered by the moderator without bothering the list, or should | |
766 have been sent to another list. | |
767 | |
768 See section '* General Information about info-* lists'. | |
769 | |
770 * bug-gnu960-request@ichips.intel.com to subscribe to bug-gnu960 | |
771 ** gnUSENET newsgroup: NONE PLANNED | |
772 ** Intel 960 Port bug reports to: bug-gnu960@ichips.intel.com | |
773 | |
774 This list distributes bug reports for, fixes for bugs in, and | |
775 suggestions for improvements in Intel's port of GNU software to the | |
776 Intel 960 microprocessor. | |
777 | |
778 You can also fax to: GNU/960 - 1-503-696-4930. | |
779 | |
780 There are no other GNU mailing lists or gnUSENET newsgroups for Intel's | |
781 port of GNU software to the Intel 960 microprocessor. | |
782 | |
783 See section '* General Information about bug-* lists and reporting | |
784 program bugs'. | |
785 | |
786 * bug-glibc-request@gnu.org to subscribe to bug-glibc | |
787 ** gnUSENET newsgroup: gnu.glibc.bug | |
788 ** GNU C Library bug reports to: bug-glibc@gnu.org | |
789 | |
790 This list distributes, to the active maintainers of glibc (GNU's C | |
791 library), bug reports and fixes for, and suggestions for improvements in | |
792 glibc. User discussion of glibc also occurs here. | |
793 | |
794 Announcements of new releases of glibc are made on both info-gcc and | |
795 bug-glibc. | |
796 | |
797 There are no other GNU mailing lists or gnUSENET newsgroups for the GNU | |
798 C Library. | |
799 | |
800 See section '* General Information about bug-* lists and reporting | |
801 program bugs'. | |
802 | |
803 * bug-g++-request@gnu.org to subscribe to bug-g++ | |
804 ** gnUSENET newsgroup: gnu.g++.bug | |
805 ** G++ bug reports to: bug-g++@gnu.org | |
806 | |
807 This list distributes bug reports for, fixes for bugs in, and | |
808 suggestions for improvements in the GNU C++ Compiler to its active | |
809 developers. | |
810 | |
811 G++ uses the GNU C-Compiler back end. Active developers may wish to | |
812 subscribe to bug-gcc@gnu.org as well. | |
813 | |
814 Subscribers to bug-g++ get all info-g++ messages. | |
815 | |
816 See section '* General Information about bug-* lists and reporting | |
817 program bugs'. | |
818 | |
819 * help-g++-request@gnu.org to subscribe to help-g++ | |
820 ** gnUSENET newsgroup: gnu.g++.help (and one-way into comp.lang.c++) | |
821 ** Send contributions to: help-g++@gnu.org | |
822 | |
823 This list is the place for users and installers of the GNU C++ Compiler | |
824 to ask for help. Please send bug reports to bug-g++@gnu.org | |
825 instead of posting them here. | |
826 | |
827 help-g++ is also gated one way to USENET's newsgroup comp.lang.c++. | |
828 This one-way gating is done for users whose sites get comp.lang.c++, but | |
829 not gnu.g++.help. | |
830 | |
831 See section '* General Information about help-* lists'. | |
832 | |
833 * info-g++-request@gnu.org to subscribe to info-g++ | |
834 ** gnUSENET newsgroup: gnu.g++.announce (and one-way into comp.lang.c++) | |
835 ** Send announcements to: info-g++@gnu.org | |
836 | |
837 This list distributes announcements and progress reports on the GNU C++ | |
838 Compiler. It is NOT for general discussion; please use help-g++ for | |
839 that. | |
840 | |
841 The list is filtered to remove items meant for info-g++-request, that | |
842 can be answered by the moderator without bothering the list, or should | |
843 have been sent to another list. | |
844 | |
845 It is also gated one way to USENET's newsgroup comp.lang.c++. This | |
846 one-way gating is done for users whose sites get comp.lang.c++, but not | |
847 gnu.g++.announce. | |
848 | |
849 Do not report g++ bugs to info-g++ or comp.lang.c++, mail them to | |
850 bug-g++@gnu.org instead. | |
851 | |
852 See section '* General Information about info-* lists'. | |
853 | |
854 * bug-lib-g++-request@gnu.org to subscribe to bug-lib-g++ | |
855 ** gnUSENET newsgroup: gnu.g++.lib.bug | |
856 ** lib-g++ bug reports to: bug-lib-g++@gnu.org | |
857 | |
858 This list distributes, to the active maintainers of libg++ (GNU's | |
859 library for C++), bug reports and fixes for, and suggestions for | |
860 improvements in lib-g++. User discussion of libg++ also occurs here. | |
861 | |
862 Announcements of new releases of libg++ are made on both info-g++ and | |
863 bug-lib-g++. | |
864 | |
865 There are no other GNU mailing lists or gnUSENET newsgroups for GNU's | |
866 G++ Library. | |
867 | |
868 See section '* General Information about bug-* lists and reporting | |
869 program bugs'. | |
870 | |
871 * info-gnu-fortran-request@gnu.org to subscribe to info-gnu-fortran | |
872 ** gnUSENET newsgroup: NONE YET | |
873 ** Send announcements to: info-gnu-fortran@gnu.org | |
874 | |
875 This list is for progress reports and release notices for G77/GNU | |
876 Fortran. | |
877 | |
878 The list is filtered to remove items meant for info-gnu-fortran-request, | |
879 that can be answered by the moderator without bothering the list, or that | |
880 should have been sent to another list. | |
881 | |
882 People on the Internet can get a current status report by fingering the | |
883 address fortran@gnu.org or by looking at the GNU Fortran web pages at | |
884 http://www.gnu.org/software/fortran/fortran.html. | |
885 | |
886 Users looking for help should ask the help-gnu-fortran@gnu.org list. | |
887 Bug reports should go to bug-gnu-fortran@gnu.org. | |
888 | |
889 See section '* General Information about info-* lists'. | |
890 | |
891 * help-gnu-fortran-request@gnu.org to subscribe to help-gnu-fortran | |
892 ** gnUSENET newsgroup: NONE YET | |
893 ** Send messages to: help-gnu-fortran@gnu.org | |
894 | |
895 This list is for user requests for help and discussion about GNU | |
896 Fortran (G77). Bug reports should go to bug-gnu-fortran@gnu.org. | |
897 | |
898 See section '* General Information about help-* lists'. | |
899 | |
900 * bug-gnu-fortran@@gnu.org to subscribe to bug-gnu-fortran | |
901 ** gnUSENET newsgroup: NONE YET | |
902 ** Send messages to: help-gnu-fortran@gnu.org | |
903 | |
904 This list is for bug-reports and patches for GNU Fortran | |
905 (G77). Requests for help should go to help-gnu-fortran@gnu.org. | |
906 | |
907 See section '* General Information about bug-* lists and reporting | |
908 program bugs'. | |
909 | |
910 * bug-oleo-request@gnu.org to subscribe to bug-oleo | |
911 ** gnUSENET newsgroup: NONE PLANNED | |
912 ** Oleo bug reports to: bug-oleo@gnu.org | |
913 | |
914 This list distributes, to the active maintainers of Oleo (the GNU | |
915 spreadsheet), bug reports and fixes for, and suggestions for | |
916 improvements to Oleo. User discussion of Oleo also occurs here. | |
917 | |
918 There are no other GNU mailing lists or gnUSENET newsgroups for Oleo. | |
919 | |
920 See section '* General Information about bug-* lists and reporting | |
921 program bugs'. | |
922 | |
923 * bug-gmp-request@gnu.org to subscribe to bug-gmp | |
924 ** gnUSENET newsgroup: NONE PLANNED | |
925 ** gmp bug reports to: bug-gmp@gnu.org | |
926 | |
927 This list distributes, to the active maintainers of gmp (the GNU | |
928 Multiple Precision Library), bug reports and fixes for, and suggestions | |
929 for improvements to gmp. User discussion of gmp also occurs here. | |
930 | |
931 There are no other GNU mailing lists or gnUSENET newsgroups for gmp . | |
932 | |
933 See section '* General Information about bug-* lists and reporting | |
934 program bugs'. | |
935 | |
936 * bug-panorama-request@gnu.org to subscribe to bug-panorama | |
937 ** gnUSENET newsgroup: NONE PLANNED | |
938 ** panorama bug reports to: bug-panorama@gnu.org | |
939 | |
940 This list is a place for users of Panorama to send bug reports, fixes | |
941 for them, and suggestions for improvements. | |
942 | |
943 See section '* General Information about bug-* lists and reporting | |
944 program bugs'. | |
945 | |
946 * help-panorama-request@gnu.org to subscribe to help-panorama | |
947 ** gnUSENET newsgroup: NONE PLANNED | |
948 ** articles to: help-panorama@gnu.org | |
949 | |
950 This list is the place for users and installers of Panorama to ask for | |
951 help. Please send bug reports to bug-panorama instead of posting them | |
952 here. | |
953 | |
954 * devel-panorama-request@gnu.org to subscribe to devel-panorama | |
955 ** gnUSENET newsgroup: NONE PLANNED | |
956 ** articles to: devel-panorama@gnu.org | |
957 | |
958 This list is a place for discussion among active developers of Panorama | |
959 API or any of its plugins. | |
960 | |
961 * bug-mana-request@gnu.org to subscribe to bug-mana | |
962 ** gnUSENET newsgroup: NONE PLANNED | |
963 ** mana bug reports to: bug-mana@gnu.org | |
964 | |
965 This list distributes, to the active maintainers of mana (the GNU | |
966 stand-alone mail reader), bug reports and fixes for, and suggestions | |
967 for improvements to mana. User discussion of mana also occurs here. | |
968 | |
969 There are no other GNU mailing lists or gnUSENET newsgroups for mana. | |
970 | |
971 See section '* General Information about bug-* lists and reporting | |
972 program bugs'. | |
973 | |
974 * bug-zebra-request@gnu.org to subscribe to bug-zebra | |
975 ** gnUSENET newsgroup: NONE PLANNED | |
976 ** zebra bug reports to: bug-zebra@gnu.org | |
977 | |
978 This list distributes, to the active maintainers of zebra (a GPLed | |
979 program to manage TCP/IP based routing protocols), bug reports, bug fixes, | |
49600
23a1cea22d13
Trailing whitespace deleted.
Juanma Barranquero <lekktu@gmail.com>
parents:
48786
diff
changeset
|
980 and suggestions for improvements to zebra. User discussion of zebra |
26119 | 981 also occurs here. |
982 | |
983 There are no other GNU mailing lists or gnUSENET newsgroups for zebra. | |
984 | |
985 See section '* General Information about bug-* lists and reporting | |
986 program bugs'. | |
987 | |
988 * bug-cfengine-request@gnu.org to subscribe to bug-cfengine | |
989 ** gnUSENET newsgroup: gnu.cfengine.bug | |
990 ** cfengine bug reports to: bug-cfengine@gnu.org | |
991 | |
992 This list distributes, to the active maintainers of cfengine (configure | |
993 BSD and System-5-like operating systems attached to a TCP/IP network), | |
994 bug reports and fixes for, and suggestions for improvements to cfengine. | |
995 User discussion of cfengine also occurs here. | |
996 | |
997 See section '* General Information about bug-* lists and reporting | |
998 program bugs'. | |
999 | |
1000 * help-cfengine-request@gnu.org to subscribe to help-cfengine | |
1001 ** gnUSENET newsgroup: gnu.cfengine.help | |
1002 ** Send contributions to: help-cfengine@gnu.org | |
1003 | |
1004 This list is the place for users and installers of cfengine to ask for | |
1005 help. Please send bug reports to bug-cfengine instead of posting them | |
1006 here. | |
1007 | |
1008 This list is also used for announcements about cfengine and related | |
1009 programs, and small but important patches. Announcements of cfengine | |
1010 releases are also made to info-gnu@gnu.org (see above) | |
1011 | |
1012 Since help-cfengine is a large list, send it only those items that | |
1013 are seriously important to many people. | |
1014 | |
1015 If source or patches that were previously posted or a simple fix is | |
1016 requested in help-cfengine, please mail it to the requester. Do NOT | |
1017 repost it. If you also want something that is requested, send mail to | |
1018 the requester asking him to forward it to you. This kind of traffic is | |
1019 best handled by e-mail, not a broadcast medium that reaches millions of | |
1020 sites. | |
1021 | |
1022 See section '* General Information about help-* lists'. | |
1023 Also see section '* General Information about info-* lists'. | |
1024 | |
1025 * bug-gnu-smalltalk-request@gnu.org to subscribe to bug-gnu-smalltalk | |
1026 ** gnUSENET newsgroup: gnu.smalltalk.bug | |
1027 ** GNU Smalltalk bug reports to: bug-gnu-smalltalk@gnu.org | |
1028 | |
1029 GNU Smalltalk is the GNU project implementation of the Smalltalk language. | |
1030 | |
1031 This list distributes, to the active maintainers of GNU Smalltalk, bug | |
1032 reports and fixes for, and suggestions for improvements to GNU | |
1033 Smalltalk. User discussion of GNU Smalltalk also occurs here. | |
1034 | |
1035 For now, new releases of GNU Smalltalk will also be announced on this list. | |
1036 | |
1037 There are no other GNU mailing lists or gnUSENET newsgroups for GNU | |
1038 Smalltalk. | |
1039 | |
1040 See section '* General Information about bug-* lists and reporting | |
1041 program bugs'. | |
1042 | |
1043 * st-next-request@laplace.eng.sun.com to subscribe to st-next | |
1044 ** gnUSENET newsgroup: NONE PLANNED | |
1045 ** Send contributions to: st-next@laplace.eng.sun.com | |
1046 | |
1047 For people interested in working on GNU Smalltalk on the NeXT. | |
1048 | |
1049 * bug-groff-request@gnu.org to subscribe to bug-groff | |
1050 ** gnUSENET newsgroup: gnu.groff.bug | |
1051 ** GNU groff bug reports to: bug-groff@gnu.org | |
1052 | |
1053 groff is the GNU project implementation, in C++, of the traditional Unix | |
1054 document formatting tools. | |
1055 | |
1056 This list distributes, to the active maintainers of groff, bug reports | |
1057 and fixes for, and suggestions for improvements to groff (and it | |
1058 component programs). User discussion of groff also occurs here. | |
1059 | |
1060 For now, new releases of groff will also be announced on this list. | |
1061 | |
1062 There are no other GNU mailing lists or gnUSENET newsgroups for groff. | |
1063 | |
1064 See section '* General Information about bug-* lists and reporting | |
1065 program bugs'. | |
1066 | |
1067 * bug-ghostscript-request@gnu.org to subscribe to bug-ghostscript | |
1068 ** gnUSENET newsgroup: gnu.ghostscript.bug | |
1069 ** Ghostscript bug reports to: bug-ghostscript@gnu.org | |
1070 | |
1071 Ghostscript is the GNU project implementation of a language and graphics | |
1072 library with a remarkable similarity to PostScript. | |
1073 | |
1074 This list distributes, to the active maintainers of Ghostscript, bug | |
1075 reports and fixes for, and suggestions for improvements in Ghostscript. | |
1076 | |
1077 For now, new releases of Ghostscript will also be announced on this list. | |
1078 | |
1079 There are no other GNU mailing lists or gnUSENET newsgroups for | |
1080 Ghostscript. | |
1081 | |
1082 See section '* General Information about bug-* lists and reporting | |
1083 program bugs'. | |
1084 | |
1085 * bug-gnu-utils-request@gnu.org to subscribe to bug-gnu-utils | |
1086 ** gnUSENET newsgroup: gnu.utils.bug | |
1087 ** GNU Utilities bug reports to: bug-gnu-utils@gnu.org | |
1088 | |
1089 This list distributes, to the active maintainers of these programs, bug | |
1090 reports and fixes for, and suggestions for improvements in GNU programs | |
1091 not covered by other bug-* mailing lists/gnu.*.bug newsgroups. | |
1092 | |
1093 See section '* General Information about bug-* lists and reporting | |
1094 program bugs'. | |
1095 | |
1096 * help-gnu-utils-request@gnu.org to subscribe to help-gnu-utils | |
1097 ** gnUSENET newsgroup: gnu.utils.help | |
1098 ** Send contributions to: help-gnu-utils@gnu.org | |
1099 | |
1100 This list is the place for users and installers of GNU programs not | |
1101 covered by other GNU mailing lists/gnu.* newsgroups to ask for help. | |
1102 | |
1103 Don't send bug reports to help-gnu-utils (gnu.utils.help); mail them to | |
1104 bug-gnu-utils@gnu.org instead. | |
1105 | |
1106 See section '* General Information about help-* lists'. | |
1107 | |
1108 * info-gnu-utils-request@gnu.org IS NOW DEFUNCT | |
1109 ** a gnUSENET newsgroup bever existed | |
1110 ** DEAD address: info-gnu-utils@gnu.org | |
1111 | |
1112 This list is dead. Announcements about GNU Utilities will be made to the | |
1113 list info-gnu@gnu.org (see above). | |
1114 | |
1115 * info-cvs-request@gnu.org to subscribe to info-cvs. | |
1116 ** USENET newsgroup: (none) | |
1117 ** CVS discussions/questions to: info-cvs@gnu.org | |
1118 | |
1119 This list is for discussion and dissemination of information about | |
1120 CVS. Please check the FAQ before posting questions, however. | |
1121 | |
1122 * bug-cvs-request@gnu.org to subscribe to bug-cvs. | |
1123 ** USENET newsgroup: (none) | |
1124 ** CVS bug reports to: bug-cvs@gnu.org | |
1125 | |
1126 This list distributes bug reports, fixes, and suggestions for | |
1127 improvements to the maintainers of CVS. | |
1128 | |
1129 * bug-dr-geo-request@gnu.org to subscribe to bug-dr-geo | |
1130 ** gnUSENET newsgroup: NONE | |
1131 ** Dr. Geo bug reports to: bug-dr-geo@gnu.org | |
1132 | |
1133 This list distributes bug reports for, fixes for bugs in, and | |
1134 suggestions for improvements in Dr. Geo to its active developers. | |
1135 | |
1136 See section '* General Information about bug-* lists and reporting | |
1137 program bugs'. | |
1138 | |
1139 * bug-fortran-mode-request@erl.mit.edu to subscribe to bug-fortran-mode | |
1140 ** USENET newsgroup: (none) | |
1141 ** Fortran mode bug reports to: bug-fortran-mode@erl.mit.edu | |
1142 | |
1143 This list collects bug reports, fixes for bugs, and suggestions for | |
1144 improvements in GNU Emacs's Fortran mode (a major mode to support | |
1145 editing Fortran source code). | |
1146 | |
1147 It is the place to report Fortran mode bugs by all users of Fortran | |
1148 mode. | |
1149 | |
1150 Always report the version number Fortran mode reports on startup as well | |
1151 as the version of Emacs. | |
1152 | |
1153 There is no info-fortran-mode list. There are no USENET gateways to | |
1154 bug-fortran-mode at this time. | |
1155 | |
1156 * info-gnus-request@flab.fujitsu.co.jp to subscribe | |
1157 ** gnUSENET newsgroup: NONE YET | |
1158 ** Send contributions to: info-gnus@flab.fujitsu.co.jp | |
1159 | |
1160 The list is intended to exchange useful information about GNUS, such as | |
1161 bug reports, useful hooks, and extensions of GNUS. GNUS is an NNTP-base | |
1162 network news reader for GNU Emacs (which also works with a news spool). | |
1163 English and Japanese are the official languages of the list. GNUS is | |
1164 quite different than gnews. | |
1165 | |
1166 * info-gnus-english-request@gnu.org to subscribe | |
1167 ** gnUSENET newsgroup: gnu.emacs.gnus | |
1168 ** Send contributions to: info-gnus-english@gnu.org | |
1169 | |
1170 The list has the same charter as info-gnus. The difference is that | |
1171 English is the only official language of the list. | |
1172 | |
1173 info-gnus-english/gnu.emacs.gnus is forward to info-gnus, but NOT | |
1174 vice-versa. | |
1175 | |
1176 * info-gnews-request@ics.uci.edu to subscribe to info-gnews | |
1177 ** gnUSENET newsgroup: gnu.emacs.gnews | |
1178 ** Send contributions to: info-gnews@ics.uci.edu | |
1179 | |
1180 This newsgroup is intended to exchange useful information about gnews, | |
1181 such as bug reports, useful hooks, and extensions of gnews. gnews is an | |
1182 NNTP-base network news reader for GNU Emacs (which also works a news | |
1183 spool). It is quite different than GNUS. | |
1184 | |
1185 * gnu-emacs-ada-request@grebyn.com to subscribe to gnu-emacs-ada | |
1186 ** gnUSENET newsgroup: NONE PLANNED | |
1187 ** Gnu Emacs Ada support bug reports to: gnu-emacs-ada@grebyn.com | |
1188 | |
1189 This list distributes bug reports for, fixes for bugs in, and | |
1190 suggestions for improvements in GNU Emacs' editing support of the Ada | |
1191 programming language. | |
1192 | |
1193 There are no other GNU mailing lists or gnUSENET newsgroups for GNU | |
1194 Emacs' editing support of Ada. | |
1195 | |
1196 See section '* General Information about bug-* lists and reporting | |
1197 program bugs'. | |
1198 | |
1199 * bug-vm-request@uunet.uu.net to subscribe to bug-vm | |
1200 ** gnUSENET newsgroup: gnu.emacs.vm.bug | |
1201 ** VM mail reader bug reports to: bug-vm@uunet.uu.net | |
1202 | |
1203 This list discusses bugs in View Mail mode for GNU Emacs, with an | |
1204 emphasis on beta and prerelease versions. | |
1205 | |
1206 Always report the version number of VM you are using, as well as the | |
1207 version of Emacs you're running. If you believe it is significant, | |
1208 report the operating system used and the hardware. | |
1209 | |
1210 Subscribers to bug-vm get all info-vm messages. | |
1211 | |
1212 * info-vm-request@uunet.uu.net to subscribe to info-vm | |
1213 ** gnUSENET newsgroup: gnu.emacs.vm.info | |
1214 ** Send contributions to: info-vm@uunet.uu.net | |
1215 | |
1216 This list discusses the View Mail mode for GNU Emacs, an alternative to | |
1217 rmail mode. | |
1218 | |
1219 * supercite-request@warsaw.nlm.nih.gov to subscribe to supercite | |
1220 ** gnUSENET newsgroup: NONE PLANNED | |
1221 ** Send articles to: supercite@warsaw.nlm.nih.gov | |
1222 *** UUCP: ..!uunet!warsaw.nlm.nih.gov!supercite-request | |
1223 | |
1224 The supercite mailing list covers issues related to the advanced | |
1225 mail/news citation package called Supercite for GNU Emacs. | |
1226 | |
1227 * auc-tex-request@iesd.auc.dk to subscribe | |
1228 ** USENET newsgroup: NONE YET | |
1229 ** Send contributions to: auc-tex@iesd.auc.dk | |
1230 | |
1231 The list is intended to exchange information about AUC TeX, such as | |
1232 bug reports, request for help, and information on current | |
1233 developments. AUC TeX is a much enhanced LaTeX mode for GNU Emacs. | |
1234 | |
1235 The list is unmoderated. | |
1236 | |
1237 * bug-gnu-chess-request@gnu.org to subscribe to bug-gnu-chess | |
1238 ** gnUSENET newsgroup: gnu.chess.bug | |
1239 ** GNU Chess bug reports to: bug-gnu-chess@gnu.org | |
1240 | |
1241 This list directly accesses the GNU Chess developer's group. If you | |
1242 have a *BUG* to report about the program, which can also include a | |
1243 feature enhancement request, please send it to this list. | |
1244 | |
1245 Subscribers to bug-gnu-chess get all info-gnu-chess messages. | |
1246 | |
1247 See section '* General Information about bug-* lists and reporting | |
1248 program bugs'. | |
1249 | |
1250 * help-gnu-chess-request@gnu.org IS NOW DEFUNCT | |
1251 ** gnUSENET newsgroup: NONE PLANNED | |
1252 ** DEAD address: help-gnu-chess@gnu.org | |
1253 | |
1254 This list is dead. Use info-gnu-chess@gnu.org/gnu.chess instead. | |
1255 | |
1256 * info-gnu-chess-request@gnu.org to subscribe to info-gnu-chess | |
1257 ** gnUSENET newsgroup: gnu.chess | |
1258 ** Send contributions to: info-gnu-chess@gnu.org | |
48786 | 1259 ** FAQ-URL: http://www.tim-mann.org/chess.html |
26119 | 1260 ** FAQ-Archive-name: games/chess/gnu-faq |
1261 ** FAQ-Posting-frequency: monthly | |
1262 | |
1263 This list is the place for users and installers of GNU Chess to ask for | |
1264 help. This list is also used for games played by people or other | |
1265 entities against the program, and other generalized non-bug, | |
1266 non-enhancement data. Please send bug reports to bug-gnu-chess instead | |
1267 of posting them here. | |
1268 | |
1269 This list is also used for announcements about GNU Chess and related | |
1270 programs, and small but important patches. Announcements of GNU Chess | |
1271 releases are also made to info-gnu@gnu.org (see above) | |
1272 | |
1273 Since info-gnu-chess is a large list, send it only those items that | |
1274 are seriously important to many people. | |
1275 | |
1276 If source or patches that were previously posted or a simple fix is | |
1277 requested in info-gnu-chess, please mail it to the requester. Do NOT | |
1278 repost it. If you also want something that is requested, send mail to | |
1279 the requester asking him to forward it to you. This kind of traffic is | |
1280 best handled by e-mail, not a broadcast medium that reaches millions of | |
1281 sites. | |
1282 | |
1283 See section '* General Information about help-* lists'. | |
1284 Also see section '* General Information about info-* lists'. | |
1285 | |
1286 * bug-gnu-shogi-request@gnu.org to subscribe to bug-gnu-shogi | |
1287 ** gnUSENET newsgroup: NONE PLANNED | |
1288 ** GNU Shogi bug reports to: bug-gnu-shogi@gnu.org | |
1289 | |
1290 This list directly accesses the GNU Shogi developer's group. If you | |
1291 have a *BUG* to report about the program, which can also include a | |
1292 feature enhancement request, please send it to this list. | |
1293 | |
1294 Subscribers to bug-gnu-shogi get all info-gnu-shogi messages. | |
1295 | |
1296 See section '* General Information about bug-* lists and reporting | |
1297 program bugs'. | |
1298 | |
1299 Shogi is a game something like chess. There are several different types | |
1300 of pieces, a board that is 9 by 9 squares, and the modification that a | |
1301 captured piece can be reintroduced on the board by the capturing player | |
1302 (and used). Due to this last difference from Western chess, a Shogi | |
1303 game never simplifies. | |
1304 | |
1305 * bug-mcsim-request@gnu.org to subscribe to bug-mcsim | |
1306 ** gnUSENET newsgroup: None at present. | |
1307 ** MCSim bug reports to: bug-mcsim@gnu.org | |
1308 | |
1309 This list is used for bug reports concerning MCSim, a general- | |
1310 purpose modeling and simulation program. It is also for user | |
1311 discussion of bug fixes and patches. | |
1312 | |
1313 This list is unmoderated. | |
1314 | |
1315 See section '* General Information about bug-* lists and reporting | |
1316 program bugs'. | |
1317 | |
1318 * help-mcsim-request@gnu.org to subscribe to help-mcsim | |
1319 ** gnUSENET newsgroup: None at present. | |
1320 ** Send contributions to: help-mcsim@gnu.org | |
1321 | |
1322 This list is the place for users and installers of MCSim to ask for | |
1323 help. Please send bug reports to bug-mcsim instead of posting them | |
1324 here. | |
1325 | |
1326 This list is also used for announcements about MCSim and related | |
1327 programs, and small but important patches. Announcements of MCSim | |
1328 releases are also made to info-gnu@gnu.org (see above) | |
1329 | |
1330 * bug-m4-request@gnu.org to subscribe to bug-m4 | |
1331 ** gnUSENET newsgroup: None at present. | |
1332 ** Send contributions to: bug-m4@gnu.org | |
1333 | |
1334 This list is used for bug reports concerning m4, the GNU implementation | |
1335 of the traditional Unix macro processor. It is also for user | |
1336 discussion of bug fixes and patches. | |
1337 | |
1338 This list is unmoderated. | |
1339 | |
49600
23a1cea22d13
Trailing whitespace deleted.
Juanma Barranquero <lekktu@gmail.com>
parents:
48786
diff
changeset
|
1340 * gpc-request@gnu.de to subscribe to gpc |
26119 | 1341 ** gnUSENET newsgroup: None at present. |
1342 ** Send contributions to: gpc@gnu.de | |
1343 | |
1344 This list is the user mailing list for GNU Pascal. | |
1345 *NOTE* This list was formerly at gpc@hut.fi, and moved as of 1999-05-13. | |
1346 Announcements will now be sent to an announcements list (see next entry) | |
1347 as well as to this list and info-gnu@gnu.org. | |
1348 | |
1349 * gpc-announce-request@gnu.de to subscribe to gpc-announce | |
1350 ** gnUSENET newsgroup: None at present. | |
1351 ** Send contributions to: gpc-announce@gnu.de | |
1352 | |
1353 This list will have announcements to interest to users of GNU Pascal, | |
1354 including new releases. | |
1355 | |
1356 * autoconf-request@gnu.org to subscribe to automake | |
1357 ** gnUSENET newsgroup: NONE PLANNED | |
1358 ** Send contributions to: autoconf@gnu.org | |
1359 | |
1360 The list can be used to discuss the autoconf build system and related | |
1361 tools (eg config.guess). The discussion can range from simple "how-to" | |
1362 questions up to patches and future directions for this tool. | |
1363 | |
1364 * automake-request@gnu.org to subscribe to automake | |
1365 ** gnUSENET newsgroup: NONE PLANNED | |
1366 ** Send contributions to: automake@gnu.org | |
1367 | |
1368 The list can be used to discuss automake and related tools (eg libtool). | |
1369 The discussion can range from simple "how-to" questions up to patches | |
1370 and configuration philosophy. | |
1371 | |
1372 * libtool-request@gnu.org to subscribe to libtool | |
1373 ** gnUSENET newsgroup: NONE PLANNED | |
1374 ** Send contributions to: libtool@gnu.org | |
1375 | |
1376 The list can be used to discuss development and porting of libtool, and | |
1377 anything else that the libtool developers might find interesting (excepting | |
1378 bug-reports which have a list of their own). | |
1379 | |
1380 This list is unmoderated. | |
1381 | |
1382 * bug-libtool-request@gnu.org to subscribe to bug-libtool | |
1383 ** gnUSENET newsgroup: NONE PLANNED | |
1384 ** Send contributions to: bug-libtool@gnu.org | |
1385 | |
1386 The list can be used to submit and to discuss bugs in libtool. The | |
1387 discussion can range from bug reports and patches themselves to discourse | |
1388 related to specific bugs and patches. | |
1389 | |
1390 This list is unmoderated. | |
1391 | |
1392 * libtool-commit-request@gnu.org to subscribe to libtool | |
1393 ** gnUSENET newsgroup: NONE PLANNED | |
1394 ** Send contributions to: libtool-commit@gnu.org | |
1395 | |
1396 The list distributes automatic reports of cvs commits to the libtool | |
1397 development sources to the list subscribers. Probably, any discussion | |
1398 related to these automatic submissions should go to the libtool list which | |
1399 has more subscribers who will see the submission. | |
1400 | |
1401 This list is unmoderated. | |
1402 | |
1403 * bug-a2ps-request@gnu.org to subscribe to bug-a2ps | |
1404 ** gnUSENET newsgroup: NONE PLANNED | |
1405 ** Send contributions to: bug-a2ps@gnu.org | |
1406 | |
1407 This list is used for bug reports concerning GNU a2ps, an Any to | |
1408 PostScript filter. People willing to help (debugging, or helping users) | |
1409 may subscribe to this list. | |
1410 | |
1411 This list is unmoderated. | |
1412 | |
1413 * a2ps-request@gnu.org to subscribe to a2ps | |
1414 ** gnUSENET newsgroup: NONE PLANNED | |
1415 ** Send contributions to: a2ps@gnu.org | |
1416 | |
1417 On this list are sent announcements about GNU a2ps --included betas--, | |
1418 discussions on the interface, implementations etc. It is by no means a | |
1419 bug reporting address, and its volume should be kept moderate. To this | |
1420 end, and to avoid `accidents' (bug reports and spam), this list is not | |
1421 moderated but members only can post. | |
1422 | |
1423 * wget-subscribe@sunsite.auc.dk to subscribe to wget@sunsite.auc.dk | |
1424 ** gnUSENET newsgroup: NONE PLANNED | |
1425 ** Send contributions to: wget@sunsite.auc.dk | |
1426 | |
1427 This list is for user discussion of wget. This list is not moderated. | |
1428 | |
1429 * help-gnu-shogi-request@gnu.org IS NOW DEFUNCT | |
1430 ** gnUSENET newsgroup: NONE PLANNED | |
1431 ** DEAD address: help-gnu-shogi@gnu.org | |
1432 | |
1433 This list is dead. | |
1434 | |
1435 * info-gnu-shogi-request@gnu.org to subscribe to info-gnu-shogi | |
1436 ** gnUSENET newsgroup: NONE PLANNED | |
1437 ** Send contributions to: info-gnu-shogi@gnu.org | |
1438 | |
1439 This list is the place for users and installers of GNU Shogi to ask for | |
1440 help. This list is also used for games played by people or other | |
1441 entities against the program, and other generalized non-bug, | |
1442 non-enhancement data. Please send bug reports to bug-gnu-shogi instead | |
1443 of posting them here. | |
1444 | |
1445 This list is also used for announcements about GNU Shogi and related | |
1446 programs, and small but important patches. Announcements of GNU Shogi | |
1447 releases are also made to info-gnu@gnu.org (see above) | |
1448 | |
1449 Since info-gnu-shogi is a large list, send it only those items that | |
1450 are seriously important to many people. | |
1451 | |
1452 If source or patches that were previously posted or a simple fix is | |
1453 requested in info-gnu-shogi, please mail it to the requester. Do NOT | |
1454 repost it. If you also want something that is requested, send mail to | |
1455 the requester asking him to forward it to you. This kind of traffic is | |
1456 best handled by e-mail, not a broadcast medium that reaches millions of | |
1457 sites. | |
1458 | |
1459 See section '* General Information about help-* lists'. | |
1460 Also see section '* General Information about info-* lists'. | |
1461 | |
1462 * bug-texinfo-request@gnu.org to subscribe to bug-texinfo | |
1463 ** gnUSENET newsgroup: NONE | |
1464 ** GNU Texinfo bug reports to: bug-texinfo@gnu.org | |
1465 | |
1466 This list distributes, to the active maintainers of these programs, bug | |
1467 reports and fixes for, and suggestions for improvements in GNU Texinfo, | |
1468 both the programs and the language. | |
1469 | |
1470 See section '* General Information about bug-* lists and reporting | |
1471 program bugs'. | |
1472 | |
1473 * help-texinfo-request@gnu.org to subscribe to help-texinfo | |
1474 ** gnUSENET newsgroup: NONE | |
1475 ** Send contributions to: help-texinfo@gnu.org | |
1476 | |
1477 This list is the place for authors, users and installers of GNU Texinfo | |
1478 to ask for help. | |
1479 | |
1480 Don't send bug reports to help-texinfo; mail them to | |
1481 bug-texinfo@gnu.org instead. | |
1482 | |
1483 See section '* General Information about help-* lists'. | |
1484 | |
1485 * gnu-manual-request@a.cs.uiuc.edu IS NOW DEFUNCT | |
1486 ** DEAD: Gnusenet newsgroup: gnu.emacs.lisp.manual | |
1487 ** DEAD address: gnu-manual@a.cs.uiuc.edu | |
1488 *** DEAD UUCP address: ..!uunet!uiucdcs!gnu-manual-request | |
1489 | |
1490 This list and newsgroup is dead. It was a working group whose | |
1491 volunteers wrote, proofread and commented on the developing GNU Emacs | |
1492 Lisp programmers manual. | |
1493 | |
1494 Send bugs in the GNU Emacs Lisp reference manual to: | |
1495 lisp-manual-bugs@gnu.org | |
1496 | |
1497 lisp-manual-bugs is neither a mailing list nor a gnUSENET newsgroup. | |
1498 It's just a bug-reporting address. | |
1499 | |
1500 * no mailing list request | |
1501 ** gnUSENET newsgroup: gnu.gnusenet.config | |
1502 ** no mailing list | |
1503 | |
1504 This newsgroup has nothing to do with GNU software, especially its | |
1505 configuration. It exists to distribute information about the | |
1506 administration and configuration of gnUSENET: the gnu.all alternative | |
1507 USENET hierarchy that carry the GNU mailing lists. | |
1508 | |
1509 Administrators of gnUSENET hosts receiving the gnu.all newsgroups are | |
1510 welcome to ask questions here or via e-mail of gnu@gnu.org. | |
1511 | |
1512 * no mailing list request | |
1513 ** gnUSENET newsgroup: gnu.gnusenet.test | |
1514 ** no mailing list | |
1515 | |
1516 This newsgroup has nothing to do with GNU software, especially its | |
1517 testing. It exists to allow test messages to be made in gnUSENET: the | |
1518 gnu.all alternative USENET hierarchy that carry the GNU mailing lists. | |
1519 | |
1520 Local variables: | |
1521 mode: outline | |
1522 fill-column: 72 | |
1523 End: |