Subject:
|
Re: group suggestion
|
Newsgroups:
|
lugnet.admin.general
|
Date:
|
Wed, 1 Sep 1999 17:39:28 GMT
|
Viewed:
|
384 times
|
| |
|
|
.announce.brickshelf makes sense since the updates are essentially
broadcasts and not really
interactive.
I was going to suggest publish.scans instead of db.scans, but
publish.scans implies discussions about any type of scans while db.scans
implies discussions about scans of official instructions/catalogs.
One alternative would be to create both .publish.moc and .publish.scans
but I think I prefer .db.scans better (since .publish is mostly moc's
anyway).
KL
Todd Lehman wrote:
>
> Or, we could even create *both* a .db.scans group (for everyone) and an
> .announce.scans or .announce.brickshelf (for Kevin, and readers), whereby
> Kevin could do this in his postings:
>
> Newsgroups: lugnet.announce.brickshelf,lugnet.db.scans
> Followup-To: lugnet.db.scans
>
> and people who wanted to hear only about updates could subscribe to the
> .announce group and ignore the .db group.
>
> --Todd
>
|
|
Message has 1 Reply:
 | | Re: group suggestion
|
| (...) Actually, .publish isn't supposed to be for talking about MOC's at all -- it's for talking about publishing per se: Photography techniques, imaging systems, WWW authoring tools, Internet service providers, legal issues, etc. Long ago, there (...) (25 years ago, 1-Sep-99, to lugnet.admin.general)
|
Message is in Reply To:
| | Re: group suggestion
|
| (...) Steve/Kevin, I'd forgotten all about this! (The messages above are from 11 months ago, and in the meantime, Kevin has been using the .publish group as the next best thing.) Since the ng hierarchy has stablized much more now since last October (...) (25 years ago, 1-Sep-99, to lugnet.admin.general)
|
8 Messages in This Thread:
 
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
