09-03-14 11:17 Roy Witt wrote to Holger Granholm about Amateur Radio Newslin

 RW> {at}MSGID: 
 RW> {at}REPLY: 
 RW> Greetings Holger!
-snip-
 HG> I always check the file for possible changes since last.

 RW> That's easy to do. Everything you need to know about the
 RW> guideline post is that there is a date when the file was last
 RW> updated, the code used to determine what, if anything, was
 RW> changed: The version number and it's last change will be at the
 RW> top of the header, so you don't need to scroll down if you
 RW> already have a copy.
-snip-
 :C indicates a change to the text since the last update was made.
 :D indicates deleted material since the last update was made.
 :N indicates new material since the last revision of the text was made.

Howdy! Roy,

When I see Rulz I look at the :C, :D and :N areas to learn what's been
updated since the last revision.

I don't save a copy of them if there isn't any changes to the last one
I saved in my text file for the echo.

I do the same thing in the Fido Gazatte echo, that's why I asked Janis
to add a Date to the top of one of the parts of the Gazette because I
seen another page that was many lines long which did have a Date at the
top telling when it was last updated.

I have been saving interesting BBS messages in text files ever since I
called BBS's on Dial-Up with a 300 baud VIC-Modem plugged in the back
of my Commodore 64 PC.

... K.C.C. (Knowledgeabele Computer Community) - The BBS Users Help Line.
--- MultiMail/MS-DOS v0.49
--- SBBSecho 2.12-Linux