Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[CQ\-Contest\]\s+to\s+dupe\s+or\s+not\s+to\s+dupe\s*$/: 3 ]

Total 3 documents matching your query.

1. [CQ-Contest] to dupe or not to dupe (score: 1)
Author: kr2q@optonline.net
Date: Fri, 01 Dec 2006 01:32:45 +0000 (GMT)
Dear DO, et al: 1. Unlike SS where you MUST send both calls, a typical qso in CQWW is: a. a bunch of guys send their call b. one station is called in reply and gets a signal report c. the "chosen" st
/archives//html/CQ-Contest/2006-11/msg00880.html (8,604 bytes)

2. [CQ-Contest] to dupe or not to dupe (score: 1)
Author: <john@kk9a.com>
Date: Thu, 30 Nov 2006 23:54:28 -0500
I agree that you should work the dupes. It is fast, harmless and it can do some good if the previous QSO was a bust. I accidentally duped one well known highly skilled operator this weekend and he si
/archives//html/CQ-Contest/2006-12/msg00001.html (9,311 bytes)

3. Re: [CQ-Contest] to dupe or not to dupe (score: 1)
Author: "Mark Beckwith" <n5ot@n5ot.com>
Date: Fri, 1 Dec 2006 08:28:15 -0600
This can be very frustrating. I think the strongest message to get across under these circumstances to the guy telling you you're a dupe is: "You're not in my log." On phone this is easy because you
/archives//html/CQ-Contest/2006-12/msg00027.html (7,857 bytes)


This search system is powered by Namazu