Article View: dfw.eats
Article #5742Re: Usenet Question
From: Simon is a controlling ass
Date: Thu, 18 Mar 2004 22:13
Date: Thu, 18 Mar 2004 22:13
21 lines
1623 bytes
1623 bytes
In article <2cqOb.939$La7.463370398@newssvr11.news.prodigy.com>, "Simon Belmont" <123@abc.xyz> writes: > How is it possible to break out a portion of a thread > and have it renamed? I've seen this occur in the past. > > As one example, in the thread called "best lunch spots in > Plano/Richardson", it would be cool to break out the part > starting with John R.Mellby's 1st post on 1/14/04 and then > rename it along with everything under it something like: > "hamburger spots in Plano/Richardson" for instance. > > By doing this we can keep the dfw.eats resource more > usable by indexing the articles into more relevant to topic > headings when the need arises. Whether it is needed for > the thread in my example can be questioned, but I would > like to know for future reference. Much more proof that you are not only a newbie, but a USENET virgin too. Only the original author can do that, dumbass.
Technical Details
Message-ID:
<c3d6v521c6n@enews4.newsguy.com>Path:
arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!news.glorb.com!logbridge.uoregon.edu!pln-w!spln!dex!extra.newsguy.com!newsp.newsguy.com!enews4References:
<2cqOb.939$La7.463370398@newssvr11.news.prodigy.com>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 110204,f2f72792c63c3443 X-Google-Attributes: gid110204,public X-Google-ArrivalTime: 2004-03-18 14:35:23 PST Path: arc1-ca.pugleaf.net!archiver1.google.com!news1.google.com!news.glorb.com!logbridge.uoregon.edu!pln-w!spln!dex!extra.newsguy.com!newsp.newsguy.com!enews4 From: Simon is a controlling ass Newsgroups: dfw.eats Subject: Re: Usenet Question Date: 18 Mar 2004 22:13:57 GMT Organization: http://extra.newsguy.com Lines: 21 Message-ID: <c3d6v521c6n@enews4.newsguy.com> References: <2cqOb.939$La7.463370398@newssvr11.news.prodigy.com> NNTP-Posting-Host: p-550.newsdawg.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii