Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[CQ\-Contest\]\s+CQ\-Contest\s+Digest\,\s+Vol\s+254\,\s+Issue\s+6\s+$Ack\s+issue$\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[CQ\-Contest\]\s+CQ\-Contest\s+Digest\,\s+Vol\s+254\,\s+Issue\s+6\s+$Ack\s+issue$\s*$/: 2 ]

Total 2 documents matching your query.

1. Re: [CQ-Contest] CQ-Contest Digest, Vol 254, Issue 6 (Ack issue) (score: 1): Author: Jack Brindle via CQ-Contest <cq-contest@contesting.com>; Date: Tue, 6 Feb 2024 11:37:56 -0600; It is easier than that. The CQ station sends their exchange first, giving the calling station a chance to request fills if needed. So we know the calling station will get the exchange. The problem th; /archives//html/CQ-Contest/2024-02/msg00077.html (8,490 bytes)
2. Re: [CQ-Contest] CQ-Contest Digest, Vol 254, Issue 6 (Ack issue) (score: 1): Author: David Hachadorian <k6ll.dave@gmail.com>; Date: Tue, 6 Feb 2024 13:14:00 -0700; If the CQ'ing station misses the exchange, all he has to do is LISTEN. The inheriting station is going to send it all again to the next guy. Decrement # by 1. Dave Hachadorian, K6LL Yuma, AZ On 2/6; /archives//html/CQ-Contest/2024-02/msg00081.html (9,073 bytes)

Current List: 1 - 2
Page: [1]