From: jjf@dsbc.icl.co.uk (J.J.Farrell) Subject: Re: This mail list in a news group 19 Jan 1997 20:27:33 -0800 Approved: cygnus.gnu-win32@cygnus.com Distribution: cygnus Message-ID: <199701200136.27464.0.cygnus.gnu-win32@dsbc.icl.co.uk> Content-Type: text Original-To: Keetnet@wilmington.net (Keet) Original-Cc: gnu-win32@cygnus.com In-Reply-To: <2.2.32.19970118222227.00683d74@wilmington.net> from "Keet" at Jan 18, 97 05:22:27 pm X-Mailer: ELM [version 2.4 PL23] Content-Length: 1026 Original-Sender: owner-gnu-win32@cygnus.com > From: Keet > > >comp.os.ms-windows.programmer.tools.gnu-win32 > >comp.os.ms-windows.programmer.win32.gnu-win32 > >cygnus.public.gnuccplusplusnt95win32.chat > > why so complex? not everyone who uses Cygnus GNU is a rocket scientist. try > something simple like: > > comp.cygnus.unix2win32 > comp.compiler.cygnus.unix2win32 > > or something along those lines. short, to the point, and makes sense. 1) there's no 'cygnus' branch currently in the hierarchy at either of the places you propose. You'll find it a lot harder to get a new hierarchy approved than just a new group in an existing hierarchy - especially one near the top level as in your first suggestion. As far as I am aware, there isn't enough going on in cygnus which is particular to them to warrant a hierarchy branch at any level. 2) the gnu-win32 project covers vastly more than a mere compiler - it wouldn't be appropriate under comp.compilers (assuming the typo in your second suggestion). Regards, jjf - For help on using this list, send a message to "gnu-win32-request@cygnus.com" with one line of text: "help".