Thomas, Your suggestion about DOTNET-DATA seems like a good one, and I would support it. However, this shows the folly of partioning the list, at all. In the absence of a DOTNET-DATA list, you might post your ADO.NET question to the DOTNET-CLR list (probably best), or you could pick one of the other two lists, depending upon your project type (what most participants will actually do). Most likely, you will be tempted to post your question to more than one list. The net effect will be confusion and/or increased total list traffic.
The problem that this list partioning is designed to solve (excessive list volume) would be fixed if we could wave a magic wand and eliminate all off- topic or personal posts. Partioning can only exacerbate the problem. .NET technology isn't mature enough yet to allow any significant fraction of the current list participants to subscribe to only one or two of the proposed lists. The correct solution is increased self-restraint, accompanied by some sort of policing. Bill On Sat, 1 Jun 2002 08:10:46 +0200, Thomas Scheidegger <[EMAIL PROTECTED]> wrote: >This is the right way, thanks! >One question: > what about ADO.NET postings? > >often they are > - SQL (language&server) problems, > - OLE DB related > - or very specific to one of the (new native) data providers! > >DOTNET-DATA ? > > > regards > Thomas > > > > >> -----Original Message----- >> On Behalf Of Ahern, Shannon >> Subject: Administrative Announcement - Please Read >> >> To deal with this, DevelopMentor has decided to repartition >> this list into a small number of more focused lists >> that each cater to particular communities of developers. > >You can read messages from the DOTNET archive, unsubscribe from DOTNET, or >subscribe to other DevelopMentor lists at http://discuss.develop.com. You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
