Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[Towertalk\]\s+The\s+case\s+for\s+a\s+static\s+line\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[Towertalk\]\s+The\s+case\s+for\s+a\s+static\s+line\s*$/: 3 ]

Total 3 documents matching your query.

1. [Towertalk] The case for a static line (score: 1): Author: bjk@ihug.co.nz (Barry Kirkwood); Date: Fri, 20 Dec 2002 17:44:43 +1300; The more I read on this, the better the case seems to be for having a = fixed line up and down the tower while working at heights. This is what arborists I have observed do as standard practice. do n; /archives//html/Towertalk/2002-12/msg00574.html (8,958 bytes)
2. [Towertalk] The case for a static line (score: 1): Author: dick.green@valley.net (Dick Green); Date: Fri, 20 Dec 2002 13:43:45 -0500; Barry, Do you secure the static line at the bottom of the tower either before or after the first ascent, or just let it hang free? Is there some sort of spring-loaded release so you can use the Pelz; /archives//html/Towertalk/2002-12/msg00590.html (10,358 bytes)
3. Fw: [Towertalk] The case for a static line (score: 1): Author: bjk@ihug.co.nz (Barry Kirkwood); Date: Sat, 21 Dec 2002 09:14:50 +1300; at suc of or tower.; /archives//html/Towertalk/2002-12/msg00600.html (13,803 bytes)

Current List: 1 - 3
Page: [1]