tower@bu-cs.BU.EDU (Leonard H. Tower Jr.) (03/17/88)
X-Home: 36 Porter Street, Somerville, MA 02143, USA +1 (617) 623-7739 X-UUCP-Path: ..!harvard!bu-cs!tower Several people have suggested that comp.lang.c++ should receive the info-g++ mailing list, to be kept up to date on GNU C++. The info-g++ mailing list is just over 2 months old and has averaged a few messages a week. The GNU Project has been successfully gating info-gnu-emacs one-way into comp.emacs for years. Please note that messages will only flow from info-g++ to comp.lang.c++, not vice-versa. info-g++ readers aren't expecting general C++ information, and the GNU Project does not have the resources to run a C++ general interest mailing list. Vote by mailing a YES or NO to comp-lang-c++-poll@prep.ai.mit.edu. ...!ucbvax!prep.ai.mit.edu!comp-lang-c++-poll for bangish sites. Please send a YES vote if you want info-g++ gated to comp.lang.c++ and a NO vote if you do not. Further comments welcome. PLEASE do NOT post your vote here, mail it in. enjoy -len PS: FYI: here is the description of info-g++ and associated mailing lists. * info-g++-request@prep.ai.mit.edu to subscribe to info-g++ ** submittal address: info-g++@prep.ai.mit.edu This list reports new releases, informations about ports and proven bug fixes to testers of the GNU C++ Compiler. * bug-g++-request@prep.ai.mit.edu to subscribe to bug-g++ ** G++ and GDB+ bug reports: bug-g++@prep.ai.mit.edu This list distributes bug reports, fixes for bugs, and suggestions for improvements in the GNU C++ Compiler and it's debugger GDB+ to their active developers. It is the place to report G++ and GDB+ bugs by all testers of G++ and GDB+. The GNU C++ Compiler is still in test release, and is NOT ready for everyday use. Always report the version number of g++, as well as the operating system and hardware. G++ uses the GNU C-Compiler back end. Active developers may wish to join bug-gcc@prep.ai.mit.edu as well. GDB+ uses much code from GDB. Active developers may wish to join bug-gdb@prep.ai.mit.edu as well. Members of bug-g++ automatically receive all info-g++ messages. * info-gcc-request@prep.ai.mit.edu to subscribe to info-gcc ** submittal address: info-gcc@prep.ai.mit.edu This list reports new releases and proven bug fixes to testers of the GNU C Compiler. * bug-gcc-request@prep.ai.mit.edu to subscribe to bug-gcc ** GCC bug reports to: bug-gcc@prep.ai.mit.edu This list distributes bug reports, fixes for bugs, and suggestions for improvements in the GNU C Compiler to its active developers. It is the place to report GCC bugs by all testers of GCC. The GNU C Compiler still has bugs in it, and is not quite ready for everyday use. Always report the version number of gcc, as well as the operating system and hardware. Members of bug-gcc automatically receive all info-gcc messages. End of article.
gore@hao.ucar.edu (Jacob Gore) (03/18/88)
I vote "no."
In fact, I'm not that crazy about the idea of having info-gnu piped into
comp.emacs. As an illustration, I point to the time when RMS's complaint
"commercial messages don't belong on this list" went out into comp.emacs, and
got people who only read comp.emacs upset...
I would, on the other hand, be all for separate gnu groups. Something like
comp.gnu.*, or maybe just gnu.* (keeping it out of mainstream Usenet for a
while, at least).
Jacob
Jacob Gore Gore@EECS.NWU.Edu
Northwestern Univ., EECS Dept. {oddjob,gargoyle,ihnp4}!nucsrl!gore