Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*IMO\s+POST\s+needs\s+a\s+change\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*IMO\s+POST\s+needs\s+a\s+change\s*$/: 3 ]

Total 3 documents matching your query.

1. IMO POST needs a change (score: 1): Author: km9p@contesting.com (Bill Fisher, KM9P); Date: Sun, 8 Sep 1996 10:10:31 -0400 (EDT); One little thing that bothers me about using TRLog is POST contest processing. The ONLY thing that bothers me about it is that it doesn't group the contest files it creates by name. A better solution; /archives//html/TRLog/1996-09/msg00020.html (7,594 bytes)
2. IMO POST needs a change (score: 1): Author: torsten@mephisto.physics.uiuc.edu (R. Torsten Clay); Date: Sun, 8 Sep 96 13:01:26 CDT; Yes! It would also make it harder to accidentally overwrite files. I also think that using a different file name for each contest (ie not LOG.DAT) would be better. In the past I've lost an entire lo; /archives//html/TRLog/1996-09/msg00023.html (7,303 bytes)
3. IMO POST needs a change (score: 1): Author: aa4ga@contesting.com (Lee Hiers AA4GA); Date: Mon, 09 Sep 1996 02:47:32 +0000; I like keeping each contest in a separate subdirectory...that way, I know all the junk in that directory belongs to that log...better for me than combining several contests in one directory like bran; /archives//html/TRLog/1996-09/msg00025.html (7,089 bytes)

Current List: 1 - 3
Page: [1]