JiscMail Logo
Email discussion lists for the UK Education and Research communities

Help for MINING-HISTORY Archives


MINING-HISTORY Archives

MINING-HISTORY Archives


mining-history@JISCMAIL.AC.UK


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

MINING-HISTORY Home

MINING-HISTORY Home

MINING-HISTORY  July 2009

MINING-HISTORY July 2009

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Reaves. Reply to Phil Newman posting 10/7/2009

From:

"Roger B. Hutchins" <[log in to unmask]>

Reply-To:

The mining-history list.

Date:

Thu, 16 Jul 2009 16:12:12 +0100

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (63 lines)

This is for those members that have been following the debate about the 
function of the long reaves on Dartmoor. I would welcome any questions.

      I agree with the first and second paragraph, but we do not know where 
the prehistoric streamworking may have ended and the Later streamworking 
began. I know that later work interrupted earlier field systems and 
settlements. This is obvious, and does not in any way help the boundary 
interpretation or hinder the trackway interpretation.
      The point has been missed regarding the termination of reaves before 
they reach the edge of the tinworkings. I can show several cases where the 
reave ends several yards short of the tin works, and there is no suggestion 
that the tinworks cut into the reave. This is not a case of the tinworks 
interrupting the reave, but the reave leading to the tinworks. The Merrivale 
example is a case in point. The reave terminates well back from the tinworks, 
then two hollow ways lead down into the tinworks one of them heads for the 
natural ford. There is no reason to suggest that the short Merrivale Reave is a 
continuation of either of the other elements of the so called "Great Western 
Reave" They are clearly separate entities and only joined by the imagination in 
order to justify  imaginary territories.
      There is no reason to suggest that the natural ford across Long Ash Brook 
postdates the abandonment of the streamworks because it traverses the 
bottom of it. There are inproved pathways on the other side that were 
probably created by the tin workers. A natural fording place will probably have 
been a natural fording place from time immemorial.
      There is no evidence that the reave has been effaced by later tinners,or 
ever continued as a boundary into the tinworks.
      I cannot find the 200 m gap in the Walkhampton common reave caused 
by tinworks. The tinworking ends a short distance below the reave. There is a 
small gap in the reave where the stream runs through . (DAoA map 46).
      The point concerning South Deepwork on the Eyelsbarrow is correct, but 
a well worn track allows access through this disturbance which meets with the 
reave in the other side. The tinworks does not interfere with through access. 
In fact hollow ways take the route down into the tinworks.
       This access explanation goes for all cases of interferance by later tin 
working. In no case to my knowledge does later working deny through access.
       I suggest that many of the hard tracks may well have coexisted with the 
reaves and that both may have continued to be used into histiorical times. 
This makes the problem of chronology irrelevant. Many of the hard tracks may 
well have been in use before the reaves were put in place for whatever 
purpose.
      A reave terminates a few yards above Wheal Franco. I cannot see how 
this this reave could ever have served as a boundary.
       I agree that reaves associated with prehistoric field systems may not 
have been for the removal of tin. However they seem to have been created 
for access rather than division. The fact that they do divide may be 
secondary. Many modern roads divide but division is not there intended 
function.These reaves are commonly open ended at the lower end which 
suggests that the field owners needed to bring nutrients up from the woodland 
to improve the nitrogen poor thin soils . Similar systems are still being used in 
the Med and Middle East. The causeways between the fields allow access to 
the fields. Perhaps this is also the reason for the narrowness of the fields. It is 
easier to spread compost over a narrow field than a wide one. These coaxial 
field systems can be be found all over Cyprus and throughout the Fertile 
Crescent.
       The intersecting causeways were pehaps intended for pack animals to 
access the system. How else can the open ends be explained. The terraced 
gardens of the Med needed similar access for similar reasons.
        In the last paragraph some the points cannot be proven. I do not 
expect to have found all the answers, but at least I can give a long list of 
situations that suggest a trackway function. 
        I have yet to recieve any evidence that the reaves were boundaries.
Roger B. Hutchins.

Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

April 2024
March 2024
February 2024
January 2024
December 2023
November 2023
October 2023
September 2023
August 2023
July 2023
June 2023
May 2023
March 2023
February 2023
January 2023
December 2022
October 2022
September 2022
April 2022
March 2022
February 2022
January 2022
December 2021
November 2021
October 2021
September 2021
July 2021
June 2021
May 2021
April 2021
March 2021
February 2021
January 2021
December 2020
November 2020
October 2020
September 2020
August 2020
July 2020
June 2020
May 2020
April 2020
March 2020
February 2020
January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
2004
2003
2002
2001
2000
1999
1998


JiscMail is a Jisc service.

View our service policies at https://www.jiscmail.ac.uk/policyandsecurity/ and Jisc's privacy policy at https://www.jisc.ac.uk/website/privacy-notice

For help and support help@jisc.ac.uk

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager