 | | IMPORTANT: newsgroup hierarchy naming
|
|
It seems there are subtle issues with the current naming scheme for groups... Some people using advanced filtering/integration software and/or special gateways are running into problems because the groups don't all exist under a single hierarchy (...) (26 years ago, 2-Oct-98, to lugnet.admin.general)
|
| |
| | Re: IMPORTANT: newsgroup hierarchy naming
|
|
(...) Another possibility is to do the above but also remove the ".build." from the names (to keep them simpler), and make "build.general" into "lugnet.build": lugnet.admin.database lugnet.admin.general lugnet.admin.statistics lugnet.announce (...) (26 years ago, 2-Oct-98, to lugnet.admin.general)
|
| |
| | Re: IMPORTANT: newsgroup hierarchy naming
|
|
(...) I like this suggestion best. (...) Better now than later! (26 years ago, 2-Oct-98, to lugnet.admin.general)
|
| |
| | Re: IMPORTANT: newsgroup hierarchy naming
|
|
(...) That sounds good. I've never done it in a case where I cared about keeping existing articles.... (26 years ago, 2-Oct-98, to lugnet.admin.general)
|
| |
| | Re: IMPORTANT: newsgroup hierarchy naming
|
|
(...) Assuming this path is going to be taken, I'm writing a script to reinject the existing articles into the new groups after renaming. The headers I'm auto-munging are: Newsgroups: Followup-To: And I'm deleting Xref: because the newsserver will (...) (26 years ago, 2-Oct-98, to lugnet.admin.general)
|
| |
| | Re: IMPORTANT: newsgroup hierarchy naming
|
|
(...) Think of it this way - having lugnet prepended to every newsgroup is a blessing in disguise in terms of clarity. For one thing, it makes VERY clear where to find the newsgroups. Cross-talk about lugnet on r.t.l is going to occur, and I feel (...) (26 years ago, 2-Oct-98, to lugnet.admin.general)
|
