Jump to ContentJump to Main Navigation
Piers GavestonEdward II's Adoptive Brother$
Users without a subscription are not able to see the full content.

Pierre Chaplais

Print publication date: 1994

Print ISBN-13: 9780198204497

Published to Oxford Scholarship Online: October 2011

DOI: 10.1093/acprof:oso/9780198204497.001.0001

Show Summary Details
Page of

PRINTED FROM OXFORD SCHOLARSHIP ONLINE (www.oxfordscholarship.com). (c) Copyright Oxford University Press, 2018. All Rights Reserved. Under the terms of the licence agreement, an individual user may print out a PDF of a single chapter of a monograph in OSO for personal use (for details see www.oxfordscholarship.com/page/privacy-policy).date: 23 January 2019

Compact of Brotherhood

Compact of Brotherhood

(p.6) 1 Compact of Brotherhood
Piers Gaveston

Pierre Chaplais

Oxford University Press

The chroniclers of the reign agree in blaming both Edward II and Piers Gaveston for all the ill that afflicted the kingdom from 1307 to 1312. Most of the blame was laid at Gaveston, who made enemies of the earls by his insults and arrogance, and above all gave evil counsel to the king. The king's main fault was that he listened only too readily to Gaveston's counsel instead of taking the advice of his English barons, as a result after six years of throne, Edward had accomplished nothing worthwhile. This chapter describes references to compacts of brotherhood, continental and English cases of adoptive brotherhood in the eleventh and twelfth centuries, and the idea of brotherhood agreement between Edward and Gaveston.

Keywords:   Edward II, Piers Gaveston, brotherhood, adoptive brotherhood, brotherhood agreement

Oxford Scholarship Online requires a subscription or purchase to access the full text of books within the service. Public users can however freely search the site and view the abstracts and keywords for each book and chapter.

Please, subscribe or login to access full text content.

If you think you should have access to this title, please contact your librarian.

To troubleshoot, please check our FAQs , and if you can't find the answer there, please contact us .