Xref: utzoo news.software.b:1257 news.misc:1302
Path: utzoo!mnetor!uunet!lll-winken!lll-lcc!ames!pasteur!agate!garnet!weemba
From: weemba@garnet.berkeley.edu (Obnoxious Emacs Weenie)
Newsgroups: news.software.b,news.misc
Subject: 3.0 drops the latest reference
Message-ID: <8040@agate.BERKELEY.EDU>
Date: 26 Mar 88 00:55:19 GMT
References: <507@fig.bbn.com> <224167cd:252b@snark.UUCP> <2015@epimass.EPI.COM> <224535ed:1259@snark.UUCP>
Sender: usenet@agate.BERKELEY.EDU
Reply-To: weemba@garnet.berkeley.edu (a small gnews-ance)
Followup-To: news.software.b
Organization: Brahms Gang Posting Central
Lines: 20
In-reply-to: eric@snark.UUCP (Eric S. Raymond)


In article <224535ed:1259@snark.UUCP>, eric@snark (Eric S. Raymond) writes:
>In article <3203@phri.UUCP>, roy@phri.UUCP (Roy Smith) writes:
>>	Why do you need either Xrefs or the history file to eliminate
>>seeing cross posted articles twice?  Why not just keep track of the inode
>>number of every article file you open?

>You are absolutely right. I will implement this,

Will this work under NNTP?

>					        it should fit neatly into the
>scheme I'm already using to support backtracking and discussion trees.

I don't know what scheme your using.  But I'd appreciate it if you didn't
break other people's schemes (ie, mine).  In particular, none of your art-
icles put the responded-to article message-id up in the "References:" line.

Thus, you responded to Roy Smith @phri, but your references make it appear
to be Joe Buck @epimass.

ucbvax!garnet!weemba	Matthew P Wiener/Brahms Gang/Berkeley CA 94720